apiVersion vs branch (v1.2 vs v1.3)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with the app.apiVersion documentation in app.md and trace how scripting API properties are exposed. Define the app.features behavior for supported and unknown feature names, including the tilemap-layer example, and document or test the expected false result for nonexistent properties.
Written by the indexing model from the issue text.
Description
The app.apiVersion is not a good way to check for API features when we have this branch of versions (e.g. v1.2 and v1.3). We think that we could add a new object to check features:
if app.features.hasTilemapLayers then
...
end
In case of a property that doesn't exist is used (e.g. app.features.nonExistentFeature) it just return false (instead of a Lua error).
- Dominant language
- No language data
- Stars
- 310
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from aseprite/api
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100