cli: make the existing app notice match what init checks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 92/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- angular, typescript
Research direction
Read printExistingAppNotice in apps/pidrang-cli/src/run-cli.ts, then compare its wording with isNewApp in apps/pidrang-cli/src/edit-app-routes.ts. Update the notice and the matching expectations in apps/pidrang-cli/src/run-cli.spec.ts; run pnpm exec nx test pidrang-cli. Done means the notice does not claim routes exist when only app.html changed, and the tests pass.
Written by the indexing model from the issue text.
Description
What is wrong
When pidrang init runs on an app that is not a fresh ng new app, it prints:
The app already has its own pages and routes, so pidrang only added the resource routes to ...
That is not always true. The app counts as "not new" when app.html is no longer the ng new welcome page or app.routes.ts has routes. An app with an edited app.html and no routes gets this sentence too.
How to see it
ng newan app, change one line ofsrc/app/app.html, keepapp.routes.tsempty.- Run
npx pidrang init: the sentence says the app has its own routes.
Where to look
- The sentence:
printExistingAppNoticeinapps/pidrang-cli/src/run-cli.ts. - What is tested:
isNewAppinapps/pidrang-cli/src/edit-app-routes.ts. - Tests:
apps/pidrang-cli/src/run-cli.spec.ts(search for "already has its own pages").
Steps
- Change the sentence so it is true in every case, for example: "This is not a new
ng newapp (app.htmlorapp.routes.tswas changed), so pidrang only added the resource routes to ...". - Update the tests that check the old text.
- Run
pnpm exec nx test pidrang-cli.
Done when
- The sentence no longer claims the app has routes when it may not.
- The tests pass.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 2
- Avg merge
- 9h 17m
- Merged PRs (30d)
- 48
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 pidrang/pidrang
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
good first issue layer: demo
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
good first issue layer: demo
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
good first issue layer: demo
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
layer: demo pkg: cli refactor
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jeanibarz/knowledge-base-mcp-server#1268 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Koenkk/zigbee-herdsman-converters#13820 ·
Maintainers usually reply within 2 days
-
[prefer-expect-resolves] autofix leaves a stray ")" when the awaited expression is parenthesizedOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jest-community/eslint-plugin-jest#2052 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Wallet functions throws TypeError when the wallet has no account IDPossibly taken @Medhansh-741 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
hiero-ledger/hiero-sdk-js#4781 · 1 comment ·
Maintainers usually reply within 1 day