Add explicit --api or --view=json option
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- express, javascript, nodejs
Research direction
Start by locating the generator's handling of the --no-view flag and the command-line option definitions. Compare the generated public folder behavior for view and API applications, then define the new option's expected output and add coverage for it if the repository has related tests.
Written by the indexing model from the issue text.
Description
Currently when the app is generated with --no-view flag, public folder with nested folders is created.
I propose to have additional option for creating APIs, to eliminate the need to remove these folders later.
What are your thoughts regarding this?
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 548
- PR merge metrics
- No merged PRs in 30d
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.
More from expressjs/generator
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
question
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
tests
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in expressjs/generator
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 ·