Implementation status&feedback
Open
Nobody has claimed this yet.
Implementations
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
We should reach out to well-known implementations of the Scripting API to understand the coverage of our functionalities and what we should prioritize.
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
Start by identifying well-known implementations of the Scripting API and comparing their functionality coverage with this project. Document the findings and use them to clarify which capabilities should be prioritized; the issue does not name files, tests, or an entry point.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100