open-feature / open-feature/openfeature.dev
Add documentation on hook hints
Open
Nobody has claimed this yet.
documentation
- Dominant language
- TypeScript
- Stars
- 65
- Forks
- 117
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 41
Description
Explain what they're for and how to use them.
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
No file, test, or entry point is named. Start by locating the existing hook-related documentation in the OpenFeature website and determine what “hook hints” refers to and which usage examples are expected. Done means the purpose and usage of hook hints are explained clearly in the appropriate documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100