Peter Solnica
Peter Solnica
Yeah let's just fix it via docs and: > We can detect when the user overrides exported modules and give a proper warning. WDYT? sounds good to me too.
We could add support for this as either a separate type or based on additional configuration. We need to use regexps to check the format and that is very slow,...
It's not that simple 😄 Check out this table to get an idea: https://docs.oracle.com/cd/E19455-01/806-0169/overview-9/index.html One of the reasons why dry-types was created was to **remove** generic coercions. We want coercions...
@Alexxfrolov this is as simple as: ```ruby [4] pry(main)> Types::Set = Types.Constructor(Set, Set.method(:new)) => # [5] pry(main)> Types::Set[["a", "a", "b", "c"]] => # ``` I'm not 100% sure we should...
It would be great to have this. If you could open a PR with fixed tests that would be awesome.
I closed this this since it was done in other PRs eventually
Just a short update that I ended up tweaking `eql?` to work like Object#eql? when just one arg is passed so it should work now in dry-logic 1.5.0.
Closing after all as this was done via #99
I don't think it should. You may want to use whatever object as the handler. Setting the namespace implicitly would make it impossible. What I would suggest instead would be...
Is it still an issue with dry-schema 1.13.0?