open-feature / open-feature/spec
Provide additional guidance on naming providers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 58
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 2
Description
Additional guidance on provider naming should be provided in section 2. Specifically, I think that the name of the provider should be the same across different language implementations. For example, the flagd provider should be called flagd in both the Go provider and the Python provider (this is currently not the case).
Additionally, the spec should probably say that the provider name should not include the word "provider" as that is redundant. So, AWS System Manager, and NOT AWS System Manager Provider.
https://openfeature.dev/specification/sections/providers#requirement-211
Contributor guide
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
Open the providers specification at section 2, especially requirement 2.1.1, and compare the naming guidance with the flagd Go and Python provider examples mentioned in the issue. Done means the specification clearly requires consistent provider names across language implementations and omits the redundant word "provider".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100