Single Account Type
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Connect is moving to a single account, moving away from the current Basic/Premium split.
To handle that change, dates of when the new service is available in test are needed.
For STRR some decisions on Platform capabilities are needed:
- [ ] Does the registering account need to be the account that gets an APIKey? If not then the checks that constrain the account/payment type can be removed.
- [ ] Updates to the account creation flows to use Premium instead of Basic are required.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the STRR account creation flows and the Platform capability questions about APIKey ownership and Basic/Premium checks. Confirm the dates when the new service is available in test, resolve the account and APIKey decisions, and verify that the account flows reflect the selected account type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100