-
Notifications
You must be signed in to change notification settings - Fork 12k
Schema validation failed: Data path "" should NOT have additional properties #11479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have some kind of a similar issue but when I run
Furthermore there is no packages version of my project :
|
I'm experiencing the same problem. "test-cypress-app-e2e": {
"root": "e2e/",
"projectType": "application",
"architect": {
"e2e": {
"builder": "ngx-cypress-builder:cypress",
"options": {
"devServerTarget": "test-cypress-app:serve",
"mode": "browser"
},
"configurations": {
"production": {
"devServerTarget": "test-cypress-app:serve:production"
}
}
},
"lint": {
"builder": "@angular-devkit/build-angular:tslint",
"options": {
"tsConfig": "e2e/tsconfig.e2e.json",
"exclude": [
"**/node_modules/**"
]
}
}
}
}
}, I get an error :
Mode is however a valid property, as seen in this example:
|
Confirming the issue, getting the following error
Though in my case I really specified nonexistent property, it would be nice for angular-cli to refer to it correctly. PS: package versions
|
So it looks like the npm package is out of date compared to master. The npm package is on 0.0.2 and the github repo version is 1.0.0. I installed it using the yarn add -D isaacplmann/ngx-cypress-builder#master but am now getting Could not find module "ngx-cypress-builder" because I don't think the files are compiled. @isaacplmann might help if we get the npm package udpated. |
@jordandlaman why are you commenting on this issue? If you run into a problem with |
@ernie58 I would have responded a lot faster, if you filed an issue directly on my repo |
Was just trying to point people in the right direction. This may sound stupid but when I was on your repo earlier I didn't see the option to submit an issue. Issue filed. |
Sorry, thanks. I'll take a look. |
Check if your apps angular.json file is valid and any changes you made to that file are correct |
another issue showing Schema validation failed with the following errors: |
For anyone having this problem while updating Ionic from 3 to 4: I had to remove "es5BrowserSupport": true from angular.json |
Schema validation failed with the following errors: [ERROR] ng has unexpectedly closed (exit code 1). |
But if I'm removing that I'm getting the below error
|
I posted a fix to a similar schema validation error in #14338 Based on these two answers on StackOverflow also related to schema validation errors :
See if that works. |
Please note that 0.12.4 is significantly older than 0.800.1. |
Apart from the error message not telling WHERE the problem is, it does tell you WHAT the problem is. I fixed one error and it gave me the next, which I fixed and so on. Angular 11 with latest packages including For me it was my angular.json e2e lint where I had to change from this
to this
|
I cant set
Version:
|
In angular.json I had:
and got
After upgrading from tslint to eslint. Luckely I was able to find this change in source control. It would be really helpful for the error to explain which invalid items are the issue.
Fixed it. But I had no way other than guessing and reviewing source control to determine what the issue was. |
Has same error when using as builder angular-builders/custom-webpack:dev-server or angular-builders/custom-webpack:browser |
Same error. Fixed by change schematics in angular.json was now "schematics": { it was mistake in word "styleext" - Intellij idea complain and highlight it (styleext or stylesheet is not allowed here). So after fix command : "ng g c component --skip-tests" became works properly |
I agree with @tamusjroyce above that the resolution to any error like this, is to simply remove declaring the variable that is being complained about in the source control in between the round brackets. E.g., the error for me was as follows:
This means that the property defined an a JSON object titled
Removing the Cheers! :) |
I had the same issue and for me the fix was to remove the So this:
Becomes this:
|
Bug Report or Feature Request (mark with an
x
)Area
Versions
Repro steps
projects/architect/<section>/options/invalid
options tooptions
inangular.json
egng build
Actual functionality
Desired functionality
The text was updated successfully, but these errors were encountered: