Get rid of xjstOption()
Open
semver: patch
status: ready
- Dominant language
- JavaScript
- Stars
- 117
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
https://goo.gl/6wUTNK
@veged @tadatuta @zxqfox `xjstOptions()` realy needed? Should we fix it or should we drop it?
Contributor guide
Research direction
Start by reviewing the linked reference and the eight comments, focusing on whether xjstOption() or xjstOptions() is still needed. Done requires an agreed decision to remove or fix it, with the affected implementation and behavior identified; the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100