-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
Consider support absolute path render with <AutoField> #1126
Comments
Hi @levi-art-rules and thanks for the idea! I definitely see it as something we'd like to have going forward, but introducing any sort of prop (with a sane name) to In the meantime, I'm thinking whether or not we could add something like CC @vazco/open-source. |
Feature flag sounds good to me. Thank you for your reply. I wonder what the timeline for pushing it will look like? |
@radekmie I think adding it as an experimental feature flag sounds good. As a side note, maybe we could make it easier for us to introduce such changes in the future by adding a mention to the docs like any props prefixed with "uniformsExperimental_" are reserved? I don't think it's a common practice or how useful that will actually be but just a random thought. |
@levi-art-rules We can't give you a timeline, sorry! @wadamek65 Do you think that we should add |
(That also means this issue is up for grabs; if you want, do send us a PR!) |
@radekmie Just |
Motivation why you'd like to see this in uniforms.
We have a use case where we want to display a field down to its sister field. Rn, because
uniforms
only supports rendering children fields within a specific field, it is not possible. In general, I think it's also beneficial to enable rendering a field given an absolute path.uniforms
already providesuseField
withoptions
to accept this option, what we need to do is to enable it insidecreateAutoField
.Examples of how others could use this feature.
Usage:
<AutoField name="lists.0.name" options={ absoluteName: true} />
Possible workarounds, if applicable.
N/A
The text was updated successfully, but these errors were encountered: