feat: full export of users, organizations, credentials and config

Open
  • Is something wrong?
#423 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend, data

Research direction

The payload names no files or tests, so start by finding where users, organizations, memberships, roles and passkey credentials are stored in the seamless-auth-api repository. The export format is not specified, so agree on it with the maintainers before writing code. Done means a full export that is documented and can be re-imported without losing data.

Written by the indexing model from the issue text.

Description

P1 safe v1.0

Why

No lock-in, including to Fells Code. Everything stored in Seamless Auth belongs to the organization running it.

What

  • Export users, organizations, memberships, roles, passkey credential IDs and public keys, external IDs, config
  • Documented format, re-importable

Done when

An organization can leave with all of its data in a documented format.

Dominant language
TypeScript
Stars
2
Forks
2
Avg merge
11h 40m
Merged PRs (30d)
104

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fells-code/seamless-auth-api

All issues in fells-code/seamless-auth-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.