• Type: Sub-task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Developer Tools

      User Data and Preferences
      Preferences, saved queries and pipelines, and data models are stored through compass-user-data, which already hides where data lives behind one interface, IUserData.

      On desktop the renderer changes its FileUserData implementation to use a contextBridge global, the APIs are IUserData-like in that they provide access to the abstracted parsed types much like the result of a fetch returns plain JS object decoded from fetch rather than this code dealing in filesystem specific calls.

      > Notes: Sergey and I discussed also seeing if there's a way that the renderer could align on calling "endpoints" for both Atlas and Desktop envs and the "endpoints" would be userData like REST calls to manage Compass backing storage. We do not want a fully "pretend" atlas in our Desktop solution because we foresee a merging of features where Desktop w/ Atlas Login potentially syncs user-data to their account or some other feature that would require separate logic, and a pretend layer would make it difficult to manage the "two worlds".

            Assignee:
            Neal Beeken
            Reporter:
            Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: