-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support recursive in get-in #30
Comments
Yes, it was reverted on purpose. Using schema-value proved too unpredictable and broke existing code: 240f8a5 |
We are interested in finding a way to support this. Ideas welcome. Some ideas here: #8 (comment) |
Could there be a separately special |
Perhaps. I think |
There is already |
Thanks. I understand the problem with "conditional", "maybe" etc. (actually will be doing some special form of get-in for my particular use case of "conditional" - it will return a union of values for all possible branches). As for "recursive" I definitely missing smth - it seems to me it would be just enough to resolve it to actual underlying schema and continue but you obviously encountered some issues with that. |
@obeah It is also somewhat unpredictable with recursive: (get-in {:a {:b (s/recursive Foo)}} [:a :b])
;; Foo
;; or (s/recursive Foo) ? |
thanks, got it. It seems that for this particular case, current implementation returns recursive, not underlying schema: But for the case when caller wants to go one or more levels deeper then it seems reasonable to resolve "recursive" to actual schema and continue. |
Hi,
it seems recursive is not supported by get-in. Was it omitted on purpose?
With small modifications it works for my use case:
The text was updated successfully, but these errors were encountered: