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
fix: Treat leading underscore as a sign of invalid identifier
There are 2 reasons for this change:
- leading underscores have special meaning and therefore we should prefix
those properties to avoid unexpected semantics
- in my particular use case my team is working with a schema which has
the following fields in an object: "field" and "_field" and current code
strips leading underscore and produces invalid data object with 2 fields
of the same name
0 commit comments