open-feature / open-feature/openfeature.dev
[DOC] enhance `evaluation API` docs to include named provider/client mapping
Open
Nobody has claimed this yet.
documentation
v0.6.0
- Dominant language
- TypeScript
- Stars
- 65
- Forks
- 117
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 41
Description
Change in the documentation
We need to add named provider/client mapping to our existing evaluation API docs.
It should include:
- adding code examples for registering a provider bound to a named client
- why this is useful/important
NOTE: we may want to wait for at least one SDK implementation so we can have code examples.
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
Start with the existing evaluation API documentation linked in the issue and check whether an SDK implementation is available for accurate examples. Done means the page explains the value of named provider/client mapping and includes code examples showing a provider registered for a named client.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100