anomalyco / anomalyco/models.dev
Feature Request: API Key pattern detection
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.7k
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 873
Description
When using the dataset to setup a provider, the expected UI is one where the provider is selected first, then model, or a substring search on model or provider is the first step.
But what if the UI allows for the user to enter the API key first?
In this case, it would be useful if the possible providers could be focused, because in many cases, the API key itself has a prefix that excludes all providers except the relevant one. Thus a UI where the API key is first entered could, in some cases, be the most efficient one.
So this is asking for an optional feature for the provider TOML where a regexp for how API keys are structured, is provided.
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 locating the provider TOML schema and the UI entry point for provider and model selection. Determine how an optional API-key regular expression would be represented and applied to narrow providers, then verify that providers without a pattern retain the existing selection flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100