Refactor member fields to nested form #3
Loading…
Reference in New Issue
No description provided.
Delete Branch "madis/dev-mongo:master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Can you please use same field names as in the object being nested? (
id
andfull_name
)I thought about it and i think it would be better to have the same field names in every object we store like this. It would allow to keep code like the search filter generic.
But if you are sure then yes, i can do id and full_name
To clarify, if for example we will also have references back to the inventory collection, it would be nice to be able to handle them the same way. We should keep the same convention in all nested references and full_name would make less sense for inventory.
Please confirm if you still want to use id and full_name or not.