Document process of using a third party react component
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react
- Domain
- documentation, frontend
Research direction
Start by reviewing the repository README and the Fable docs to find the appropriate documentation location. Document how to declare props for third-party React components, and clarify any relevant limitations or usage patterns for higher-order components; done means a newcomer can follow the section to use such a component.
Written by the indexing model from the issue text.
Description
I think one of the big advantages of using Fable and React over e.g. Elm is that it is possible to use an ocean full of ready made React components. However, it is somewhat unclear what needs to be done to declare the required props etc. to use a third party React component. It would be great if this repo in the readme or the Fable docs could have a section on how to do this.
I don't know what the potential issues are with various kinds of e.g. Higher Order Components etc but it might be worth spelling these out explicitly as well. Please let me know if there is anything I can help with in particular to bring this forward.
- Dominant language
- F#
- Stars
- 277
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from fable-compiler/fable-react
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
fable-compiler/fable-react#243 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fable-compiler/fable-react#241 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
fable-compiler/fable-react#240 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
fable-compiler/fable-react#239 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
fable-compiler/fable-react#236 ·
All issues in fable-compiler/fable-react
Similar issues
-
area:breg criticality:p3 documentation triage:needs-implementation
Difficulty 1/5 Under an hour Newbie friendliness 86/100
registrystack/registry-stack#1713 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
posit-dev/ggsql#565 · 1 reaction ·
Maintainers usually reply within 1 day
-
documentation easy good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lacs-project/sysknife#518 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
qgis/QGIS-Plugins-Website#459 ·
-
bot-found documentation priority: P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
madenvel/KalinkaPlayer#178 ·