Open paulbalomiri opened 8 years ago
First commit seems cool, I need to look at it more in a bit. The second commit has something I don't recognize--data.string
--is this something you're using personally?
sorry, no data schema i'm going to correct that (i did, but did not push, sorry)
These changes allow for customizing of the store. From the comments i understand that you are planning a store package?
The next changes will make arrays available, as my current implementation hacks around the problem by using subforms for each array member.
The problem: one validation context for all array.$.member
I think the way to go forward is to introduce data paths and schema paths where data paths are resolved into schema paths using info from the template instance.
Update: The schemaContext of each element should validate only the array element it represents
Part of it proposed in #98
solution to #99 (just the
distance < 6
removal part)