Toolkit: Notices API
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
Feels like a little separate API that just exists next to the Toolkit. Separate in the sense that notices aren't automatically "force" enabled for everyone, but something that an implementor has to explicitly opt-in and build somehow.
Only Problem: Some nested call inside bootstrapping or toolkit-info is adding additional data to the Notice provider. Might need a small redesign.
My gut feeling is that would be exposed via a property on Toolkit. Potentially some options during Toolkit creation to enable/disable.
Contributor guide
Research direction
Start by tracing the Toolkit, toolkit-info, and Notice provider paths mentioned in the issue to understand where nested bootstrapping calls add notice data. Done means the opt-in Notices API and its enable/disable behavior are clearly defined, including how those nested calls are handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100