Skip to content

fix(mongo): inspector $set must not treat dotted field names as paths #872

Description

@ZhuchkaTriplesix

Summary

Field inspector Save does $set: { field: value } with the card’s top-level key verbatim. MongoDB treats "a.b" as a nested path, not a literal key a.b. Editing such a field can rewrite a different subtree while the UI still shows the dotted name.

Inspector $set of one field remains on updateDocument (#778 out of scope). This is a separate corruption class.

Scope

  • Escape / literal-key $set for dotted top-level names (or refuse Save with an explicit error).
  • Test: document { "a.b": 1 } field save does not create nested a: { b: … }.

Out of scope

  • Nested document editing in the inspector.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingerror-handlingTheme parser epic label: error-handlingfrontendTheme parser epic label: frontend

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions