fix(misc): update artifact generator option descriptions and cleanup leftovers

[leosvelperez]

• Update artifact generator schemas:
  • Clarify path is the artifact file path relative to the current working directory
  • Clarify name is the artifact symbol name
  • Remove prompt for name and remove it from the important options (won't be displayed by default in Nx Console generation UI, it will be part of the collapsed options) given that most of the time, it's meant to match the filename (last segment of the path)
  • Remove some leftover options related to the name and path formats that were previously missed
• Fix an issue with NestJS generators
• Fix an issue with Next page generator

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Nov 27, 2024 1:33pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 0122138. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 7 targets

• nx affected --targets=lint,test,build,e2e,e2e-ci --base=b018b9409630e25788754b3c1945ffdc90a36411 --head=0122138bf284406199489642acf6b7872c9b5ac3 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=b018b9409630e25788754b3c1945ffdc90a36411 --head=0122138bf284406199489642acf6b7872c9b5ac3
• nx-cloud record -- nx-cloud conformance:check
• nx-cloud record -- nx sync:check
• nx documentation --no-dte
• nx affected -t e2e-macos-local --parallel=1 --base=b018b9409630e25788754b3c1945ffdc90a36411 --head=0122138bf284406199489642acf6b7872c9b5ac3

---

Sent with 💌 from NxCloud.

[mandarini]

I still think the name path is confusing, to be honest. To understand what it is, you need to carefully read the description. I think for such a widely used and simple generator, one should not need to read the description. It should be self explanatory. I would argue we keep the name as the default and prompted property (and infer the path from the name), and leave the path as optional and not prompted. The angular component generator only prompts for name, and I think we should keep that. Maybe I am wrong. I am trying to look at this from an outsider/user perspective.

[mandarini]

I think we should keep this, remove the path prompt.

[jaysoo]

Where to generate the component? ?

[leosvelperez]

I considered that one, but it is less explicit about the fact that the option is meant to be a file path. I find it more ambiguous. While the current one explicitly asks for a file path.