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
This would be great. Not only does it match how you would access an actual JS object (socialGraph.users[0]), but libs like Formik use this notation as well for its paths.
to add 2p., bracket notation could be used interchangeably and also, it could be used to escape dots in key names — if you pass a[0] you mean { a: [x] } but if you pass string, it means it's escaped object key name — a["b.c"] means {a: { "b.c": "x" }}
Numbers as indexes - that's the natural way of resolving array elements, i.e. natural because properties-numbers are treated as indexes directly, without any extra work.
Adding support for [] isn't just an extra parsing, but a heavy one, with most likely use of RegEx. As a result, it will be quite an impact on performance.
P.S. My tests showed this library is already quite slow as it is.
No description provided.
The text was updated successfully, but these errors were encountered: