Kevin
Just wanted to say that (2) would be a great addition. Given that our codebase is made up of almost entirely `Literal::Attribute`s and `Literal::Data`s, a specific type violation can be...
Maybe: ``` Person#initialize Type mismatch for prop `name` Expected: `String` Actual: `Integer(1)` ``` Here's Sorbet's type error: https://sorbet.org/docs/error-reference#7002 Edit: `prop` instead of `argument`
We use literal this way across our codebase and don't have any issues. It's a bit confusing with positional arguments but otherwise works great.
> in some of my projects I would consider a type-less prop declaration to be an error. Agree with this sentiment. I would want this feature to be opt-in. Also...
@adrianthedev why not just use `ActiveModel::Attributes`?