You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the data passed to HeadlessForm is a POJO, the field's @name is required to be a key of this POJO.
But when the data is an EmberChangeset, @name only needs to be a string.
Is this a limitation of HeadlessForm, or do I need to do some TS setup to achieve the same behaviour ?
The workaround I have found for the time being is to cast the changeset to the type of its underlying data. This brings back the @name argument type checking, but poses another issue when using validation on the form.
When the data passed to
HeadlessForm
is a POJO, the field's@name
is required to be a key of this POJO.But when the data is an EmberChangeset,
@name
only needs to be astring
.Is this a limitation of
HeadlessForm
, or do I need to do some TS setup to achieve the same behaviour ?The text was updated successfully, but these errors were encountered: