Kilian Panot

A very temporary workaround can be to give the path of your generator in a script: ```json { "scripts": { "resolve": "node -e 'console.log(require.resolve(process.argv[1]));'", "generate": "yo $(yarn resolve generator-my-generator)" }...

Due to breaking change in the interface removal, the fix will be completely effective in v11

There is actually a `tsconfig.json.template` in the **library** generator: - https://github.com/AmadeusITGroup/otter/blob/main/packages/%40o3r/workspace/schematics/library/templates/ng/tsconfig.json.template Is it an issue only in Nx workspace? Or an issue in the template generation globally?

The following items are missing to the feature: - [x] Documentation in `docs/` folders and in the list of the schematics in `readme.md` files - [x] An ngAdd option to...

> No recommendation of the pipeline. No doc / setup for dependency / source code scanning (npm/yarn audit, CodeQL etc.) Is related to the feature #689 .

Hi @khardikk , Sure you can you can work on the task. please do assign it to ourself before starting. To reply to your question: it is depending of the...

@khardikk , My bad, I did not realize you need the permission for it. I have now assigned the issue to you.

Hi @khardikk , If a link is targeting a document that does not exist (or part of an non-accessible repository) but a documentation matching matching the link is present in...

It seems that we have the similar issue on `@ama-sdk/core`

The PR #1113 is fixing the SCSS build issue but the removal of the dependency at workspace level is providing this error in `server` task: ```shell Unchanged output files: 2...