Skip to content

hub-client: redo the project selection component #85

@cscheid

Description

@cscheid

Things to consider:

  • hide the sync server choice
  • add more information ("last accessed" is something we can do with local storage; last updated might require querying the automerge document id, but I think is also doable)
  • create a per-user automerge document that stores your own "project set", and use that to store the information that we currently put on indexeddb. Then, in indexeddb we store this automerge id, allowing you to more easily have the same view over different browsers. This will also allow hosted deployments to work more uniformly (in a hosted deployment, the hosted server can manage this automerge id instead of browser-local storage.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions