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
{{ message }}
This repository has been archived by the owner on Mar 5, 2018. It is now read-only.
Whenever a path is generated and jjve blindly assumes that non-array values can be accessed using dot notation. jjve.js#L245 It would be great to use bracket notation for property names that are not valid for use with dot notation. For example, $.models.Order Stuff.description should be $.models['Order Stuff'].description.
The text was updated successfully, but these errors were encountered:
Have you looked at substackjs-/traverse? It computes paths as an array of numbers/strings. Maybe a structure like that would make more sense because you wouldn't need to parse the path string to figure out how to get at the particular object path. So instead of $.models.Order.description you'd have ['models', 'Order', 'description']. I think some way to reuse the path to find the offending object path would be great.
Whenever a path is generated and jjve blindly assumes that non-array values can be accessed using dot notation. jjve.js#L245 It would be great to use bracket notation for property names that are not valid for use with dot notation. For example,
$.models.Order Stuff.description
should be$.models['Order Stuff'].description
.The text was updated successfully, but these errors were encountered: