Design REST API for Studio Redesign
Open
delta
design
feature
- Dominant language
- Scala
- Stars
- 301
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] data model
- [ ] endpoints
- [ ] evaluate whether REST API is sufficient or if we need to consider other options (e.g. graphql)
Contributor guide
Research direction
Start with the data-model and endpoint checklist in the issue; no files or tests are identified. Define the data model and endpoints, then evaluate whether REST is sufficient or whether GraphQL should be considered. Done means the API design and that decision are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, scala
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100