open-feature / open-feature/js-sdk
Clarify/Expand on framework support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 282
- Forks
- 72
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 16
Description
JS SDK's are used in a huge variety of runtimes:
- Vanilla JS
- Client side frameworks (e.g. React, Vue, Angular) with multiple versions and paradigms
- Hybrid client/server side frameworks (e.g. Next.js)
- Mobile devices (e.g. React Native, Ionic)
- And others!
It would be good to clarify what support, if any, we provide to each of these runtimes, as well as if there are any specific affordances (e.g. additional API interfaces etc) to working with each one.
A lot of this work could/would be just documentation, but occasionally it might be necessary to add additional interfaces/hooks etc.
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 files, tests, or entry points are named. Start by reviewing the SDK documentation and existing public interfaces to inventory runtime support, then define the framework coverage and any needed affordances; done means each listed runtime has clear support guidance and any interface work is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, javascript, nextjs, react, react-native, typescript
- Domain
- documentation, frontend, mobile, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100