Why you export routes as a function
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, react, webpack
Research direction
Start with client/pages/routes.js at line 43 and read how the routes export is used in the repository. Document why it is exported as a function, with an example or usage reference if the existing code provides one; the issue is done when that explanation is available to readers.
Written by the indexing model from the issue text.
Description
I don't understand, why routes.js as exported as an function?
- Dominant language
- JavaScript
- Stars
- 294
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
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.
More from ModusCreateOrg/react-dynamic-route-loading-es6
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 25/100
ModusCreateOrg/react-dynamic-route-loading-es6#4 · 2 comments ·
All issues in ModusCreateOrg/react-dynamic-route-loading-es6
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·