These are chat archives for dry-rb/chat
defining schemas in the controllers would be too messy I think, so we could have some simpler and more concise API that would set up validation schemas behind the scenes and cache them (rebuilding schemas on each request makes no sense)
What I do in rails w/ dry-validation is set up a validations folder with schemas in it. What do you think the advantage would be setting them up behind the scenes?
is_a?in ruby you should consider this as a code smell, I hate it every time I use it :laughing:
#is an alias