Provide all functions with direct voxel coordinates
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 192
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
The implementation currently has a built-in assumption of "cubesize", which is how many world coordinates a voxel takes. However, the library can very well be used for cases where there are no world coordinates in addition to the voxel coordinates. I would suggest providing all functions with versions that take in direct voxel coordinates, and making it clear that cubesize is optional.
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.
Research direction
Start by auditing the library's functions for the built-in cubesize assumption and identify which APIs currently require world coordinates. Define the direct voxel-coordinate versions and how cubesize becomes optional. Done means all relevant functions support direct voxel coordinates without requiring world-coordinate scaling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100