microsoft / microsoft/maker.js
Dynamically modifying the range limits of a metaParameter
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 302
- Avg merge
- 21h 28m
- Merged PRs (30d)
- 5
Description
Its currently possible to initialize the max limit of a range metaParameter with a number:
But, would it be possible to dynamically modify the max based on another value by maybe passing in a function instead?
eg.
- https://maker.js.org/playground/?script=https://gist.githubusercontent.com/yertto/bf3fde0e78ea3b9b36000d7a55b14677/raw/c9914d84374ceb95f19083b02c31d5ac94d628fa/nut.js
- https://gist.github.com/yertto/bf3fde0e78ea3b9b36000d7a55b14677
This is a made up example of a nut (🔩), where the aim is to limit the maximum hole size to always be smaller than the outer hexagon.
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 with the imetaparameter API documentation for the max range limit and run the linked Maker.js playground example and gist. Determine how a limit derived from another value should behave; the work is done when the nut example can keep its hole size below the outer hexagon and the supported behavior is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100