nrwl / nx

Smart Monorepos · Fast CI
https://nx.dev
MIT License
23.28k stars 2.32k forks source link

resource schematics #4456

Closed guiseek closed 3 years ago

guiseek commented 3 years ago

resource schematics (from nestjs, not nrwl / nest).

Current Behavior

when using the nestjs schematics, resource function, returns this error:

Property 'flat' does not match the schema. 'false' should be a 'undefined'.

However the flat field is changed and continues with the same problem, I was in doubt if it opened here or in the nestjs repository.

Expected Behavior

In the last version (10) it was working.

Steps to Reproduce

Failure Logs

> Executing task in folder mycompany: ng generate @nestjs/schematics:resource --name=team --path=src/app --sourceRoot=apps/server --no-interactive --dry-run <

Property 'flat' does not match the schema. 'false' should be a 'undefined'.
The terminal process "/bin/bash '-l', '-c', '/Users/guiseek/dev/workspaces/mycompany/node_modules/.bin/ng generate @nestjs/schematics:resource --name=team --path=src/app --sourceRoot=apps/server --no-interactive --dry-run', 'ng generate @nestjs/schematics:resource --name=team --path=src/app --sourceRoot=apps/server --no-interactive --dry-run'" terminated with exit code: 1.

Environment

Node : 14.9.0 OS : darwin x64 npm : 6.14.10

nx : Not Found @nrwl/angular : 11.0.20 @nrwl/cli : 11.0.20 @nrwl/cypress : 11.0.20 @nrwl/devkit : 11.0.20 @nrwl/eslint-plugin-nx : Not Found @nrwl/express : Not Found @nrwl/jest : 11.0.20 @nrwl/linter : 11.0.20 @nrwl/nest : 11.0.20 @nrwl/next : Not Found @nrwl/node : 11.0.20 @nrwl/react : Not Found @nrwl/schematics : Not Found @nrwl/tao : 11.0.20 @nrwl/web : Not Found @nrwl/workspace : 11.0.20 typescript : 4.0.5

vsavkin commented 3 years ago

Thank you for submitting the issue.

This is the fix: https://github.com/nrwl/nx/commit/8a88fc8c71ae6e59fd65fbc0e4d84477b3322b4e

It will be in a patch release later this week.

guiseek commented 3 years ago

Thank you for submitting the issue.

This is the fix: 8a88fc8

It will be in a patch release later this week.

I wanted to correct it, but the last few days have been very busy at work, thanks for your attention!

github-actions[bot] commented 1 year ago

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.