Its a bit odd that we have Get
which accepts three styles of specifying paths, but doesn't use Paths
, and also have PickDeep
etc which use Paths
and only accepts a single style of specifying paths.
Paths
is used to validate that the specified paths are valid options + used to give intellisense, both which are handy.Paths
only supports the foo.0.bar
style of paths whereas Get
also supports foo[0].bar
and ['foo', '0', 'bar']
, is that maybe overkill for Get
? Or, if useful, should Paths
etc be extended with the same functionality?Ideally Get
and Paths
/ PickDeep
etc should behave the same when it comes to paths and use the same fundamentals.
PickDeep
and Get
feels fairly similar in other ways as well β maybe one could adapt the internals of PickDeep
to also serve Get
?
I gave it a look and a try but got a headache and needs to bang my head against something right now.
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too