lelandrichardson / lelandrichardson/react-primitives
Document extensions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.1k
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
Two kinds of extensions as described in https://youtu.be/hNwQPJy-XZY:
- How to make an existing or new primitive component work on more platforms - 17:27 (t=1047 seconds)
- Example of adding a new checkbox extension - 19:17 (t=1156 seconds)
The trick is that for each primitive there would be JavaScript files such as:
index.js- for web platform (usingreact-native-web)index.android.js- for Android (usingreact-native)index.ios.js- for iOS (usingreact-native)- ...
I was not aware of this support for either of the two kinds of extensions until very recently (unfortunately I lost track of which discussion I found https://youtu.be/hNwQPJy-XZY in). I hope we can get this more formally documented in the near future.
P.S. Here are some examples of new "primitive" components (first 2 by myself):
This description was also updated to make it clear that I meant there are two types of extensions: adding new "primitive" components and supporting additional platforms.
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 reviewing the linked video at 17:27 and 19:17 and the platform examples listed in the issue: index.js, index.android.js, and index.ios.js. Document both extension types—adding primitive components and supporting additional platforms—with examples such as react-primitives-input, react-primitives-scrollview, and react-primitives-svg; done means the extension process is formally explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100