ModusCreateOrg / ModusCreateOrg/react-dynamic-route-loading-es6
Why you export routes as a function
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 294
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
I don't understand, why routes.js as exported as an function?
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 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.
Assessment
- Tech stack
- javascript, react, webpack
- Domain
- frontend, web-dev
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100