Peter Solnica
Peter Solnica
This will be addressed in Hanami 2.0. This method will be gone as it has confusing behaviors like you noticed.
@antstorm we'll be posting an official roadmap/timeline very soon! I recommend following Tim's updates on [his blog](https://timriley.info/writing/) too. You can also see [our Trello board](https://trello.com/b/lFifnBti/hanami-20) to get a sense of...
I'd say we should raise an error, as in, we should not infer an attribute when ruby type is nil, then you'll get an 'attribute missing error' and you'll know...
Is this still relevant?
Oh I was aware of this and even had plans to address it before 1.0.0 😭 It somehow got under the radar! Don't you think this could be improved in...
@flash-gordon right, you've made really good points! I'll give it some more thoughts...at some point...in the future. Maybe something to address in 3.0.0. I'd keep this one open for the...
Thanks for this detailed report, this is clearly a bug in error handling logic in `Sum` type although I can't tell why it's happening after having a quick look at...
Oh boy, now I remember it's not the first time when I'm getting confused by this :( Maybe we should improve the error message? Like "input violates constraints of all...
Wait, this is counter-intuitive. I would expect this to work. Given that `Types::Params` works, why re-opening the module does not?
@flash-gordon do you know if it's possible to define regular modules for `Param` `JSON` etc.? It feels like we're violating POLS here.