You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: Since the change was introduced to cast id to _id in nested and embedded documents, any platforms that were using an id field anywhere in a nested / embedded document will find much of their model logic impacted negatively. As Laravel didn't support (or not very well) the standard concept for creating models for nested docs as you would with SQL and tables / relations, it would be fairly normal to have a field in any of the documents as id.
Steps to reproduce
Save any model that has a nested document with a field named id and you will find it saved as _id
Expected behaviour
Whilst I understand this is now expected behaviour based on the update introduced, it should be something that can be disabled globally. The work required to cast this on a per model basis with deeply nested objects is quite large, and should not be an acceptable solution.
Actual behaviour
As above
A global override should be added to allow people to take advantage of the updates without such large breaking changes.
The text was updated successfully, but these errors were encountered:
Description: Since the change was introduced to cast id to _id in nested and embedded documents, any platforms that were using an id field anywhere in a nested / embedded document will find much of their model logic impacted negatively. As Laravel didn't support (or not very well) the standard concept for creating models for nested docs as you would with SQL and tables / relations, it would be fairly normal to have a field in any of the documents as id.
Steps to reproduce
Expected behaviour
Whilst I understand this is now expected behaviour based on the update introduced, it should be something that can be disabled globally. The work required to cast this on a per model basis with deeply nested objects is quite large, and should not be an acceptable solution.
Actual behaviour
As above
A global override should be added to allow people to take advantage of the updates without such large breaking changes.
The text was updated successfully, but these errors were encountered: