Strict API
- Dominant language
- JavaScript
- Stars
- 330
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
Strict API prevents user to use incompatible parts of API together.
It throws exceptions when user try to
- change permanent mod on runtime
- use BEMJSON special field without compatible or with incompatible mod
- use public methods with wrong arguments
From discussions on working meetings with @veged @dfilatov @narqo.
Contributor guide
Research direction
Start by reviewing the Strict API proposal and the discussions referenced in the issue. Clarify the expected behavior for permanent mods, BEMJSON special fields, and public methods with wrong arguments before locating the relevant component APIs. Done means the incompatible combinations are defined and strict failures are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100