Credential types list should be pre-populated (caching?)
Open
Nobody has claimed this yet.
For Consideration
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
- When I click "new credential" the list of available credential types (defined in adaptors and custom types file) is pre-populated with adaptors the instance already knows about.
- When I click on an adaptor that doesn't have a JSON schema packaged from NPM, it tells me "hey, no schema defined... wanna create a raw JSON credential?")
Consider:
- what's the caching strategy for adaptors in general?
- how do we handle changes to adaptor credential schemas? (versions?)
- how/where do we define schemas that aren't linked to specific adaptors
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the “new credential” flow and how adaptor and custom types are discovered. Review the caching strategy, JSON schemas packaged from NPM, and the questions about schema versions and adaptor-independent schemas. Done means the project has an agreed implementation for discovery, caching, schema changes, and standalone credential schemas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100