[feat]: three should extend the catalogue of r3f
Open
Nobody has claimed this yet.
area: three
kind: request
- Dominant language
- TypeScript
- Stars
- 29.1k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
A clear and concise description of what the feature is
Say I my make my own native three element in r3f:
const ImageFadeMaterial = shaderMaterial(uniforms, vertexShader, fragmenShader);
extend({ ImageFadeMaterial })
Then at the very least, it would be good that typescript new this component could be animated, or even better it would be great if the component was added to the animated object we export:
<animated.imageFadeMaterial />
Why should this feature be included?
Including this feature would make a more seamless integration between r3f & rs
Please provide an example for how this would work
No response
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
The issue names shaderMaterial, extend, and the exported animated object, but provides no files or tests. Start by tracing those entry points and determine how custom r3f elements are currently typed and animated. Done would mean a custom ImageFadeMaterial can be animated, with the requested integration exposed through animated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, three.js, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100