-
-
Notifications
You must be signed in to change notification settings - Fork 666
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
vue/func-call-spacing
schema invalid
#2618
Comments
It might just be a schema configuration bug that needs to be fixed upstream. more info it.only("throw invalid defaults in rules", () => {
const ruleWithInvalidDefaults = {
meta: {
schema: {
anyOf: [
{
type: "array",
items: [
{
type: "string",
enum: ["never"]
}
],
minItems: 0,
maxItems: 1
},
{
type: "array",
items: [
{
type: "string",
enum: ["always"]
},
{
type: "object",
properties: {
allowNewlines: {
type: "boolean",
default: false
},
optionalChain: {
type: "object",
properties: {
before: {
type: "boolean",
default: true
},
after: {
type: "boolean",
default: true
}
},
additionalProperties: false
}
},
additionalProperties: false
}
],
minItems: 0,
maxItems: 2
}
]
},
},
create: () => ({})
};
assert.throws(() => {
ruleTester.run("invalid-defaults", ruleWithInvalidDefaults, {
valid: [
{
code: "foo",
options: [{}]
}
],
invalid: []
});
}, /Schema for rule invalid-defaults is invalid: default is ignored for: data1\.allowNewlines/u);
}); |
Hmm, but their test cases also pass only one option: https://github.com/eslint-stylistic/eslint-stylistic/blob/main/packages/eslint-plugin/rules/function-call-spacing/function-call-spacing._js_.test.ts |
I haven't compared them in detail, but seems like |
So I'll report this to eslint-stylistic. Thanks for your help investigating! |
I've opened an issue and a PR in eslint-stylistic:
I'll leave this issue open until a fixed version of eslint-stylistic is released. |
Yesterday, tests in all PRs started to fail for the
vue/func-call-spacing
extension rule, e.g. here: https://github.com/vuejs/eslint-plugin-vue/actions/runs/11925499375/job/33237692823?pr=2611It is likely related to changes in eslint-stylistic v2.11.0, since with
@stylistic/eslint-plugin
v2.10.1, the tests still pass.Relevant changes: eslint-stylistic/eslint-stylistic@
v2.10.1...v2.11.0
#diff-b89bec3716Unfortunately, I can't figure out how those changes influence our extension rule and tests, so @ota-meshi (or anyone else), could you please have a look at that?
The text was updated successfully, but these errors were encountered: