Skip to content
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

addRelation function do not support nested paths #444

Open
grinsteindavid opened this issue Aug 29, 2024 · 0 comments
Open

addRelation function do not support nested paths #444

grinsteindavid opened this issue Aug 29, 2024 · 0 comments

Comments

@grinsteindavid
Copy link

I am experiencing a limitation with the addRelation function when working with nested fields in my schema. Specifically, addRelation does not seem to support fields that are deeply nested using dot notation, such as remote.budgets.notifyTo.

The only way I have found to work around this limitation is to replace the dots with underscores, resulting in a field like remote_budgets_notifyTo{_id firstName}. However, this workaround is not ideal as it deviates from the more intuitive and standard nested structure.

I would prefer to use the following nested structure:

remote { budgets { notifyTo { _id firstName } } }

Is there any plan to support this feature in future releases? It would greatly improve the flexibility and readability of the schemas.

Thank you!

@grinsteindavid grinsteindavid changed the title addRelation nested attributes addRelation function do not support nested paths Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant