max-mapper / max-mapper/voxel-engine
API improvements/when can we declare 1.0
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 217
- PR merge metrics
- No merged PRs in 30d
Description
A good discussion is here: https://gist.github.com/maxogden/5009821
Many of those points are still valid, e.g. I'd like to have better streams support
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 reading the linked gist and comparing its still-valid points with the engine's current API, especially streams support. Done would require a concrete, agreed set of API improvements and criteria for declaring version 1.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100