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
There would be no way create a rule to target the first name field with this library.
Looks like using "." as a separator only is baked pretty deep here. I think a reasonable solution would be a greedy check of properties in the schema. If I pass a field with key "foo.bar" the first thing should not be to check a separator like var separator = "foo.bar".indexOf("."); it should be to see if schema.properties["foo.bar"] exists.
Expected is that I can create a rule like the following:
Given a valid schema like the following:
There would be no way create a rule to target the first name field with this library.
Looks like using "." as a separator only is baked pretty deep here. I think a reasonable solution would be a greedy check of properties in the schema. If I pass a field with key "foo.bar" the first thing should not be to check a separator like var separator = "foo.bar".indexOf("."); it should be to see if schema.properties["foo.bar"] exists.
Expected is that I can create a rule like the following:
Actual is an error:
"first not defined in properties"
The text was updated successfully, but these errors were encountered: