- Issue created by @tr
- πΊπΈUnited States tr Cascadia
Only thing left is this:
/builds/project/rules/web/modules/custom/rules/config/schema/rules.context.schema.yml 25:3 error Empty mapping values are forbidden yml/no-empty-mapping-value
And the comments in
rules.context.schema.yml
mention that the mapping value was deliberately left empty, so I don't want to change that.However, it would be nice to be able to suppress this one eslint error message in this one location, like we can with cspell:ignore or phpcs:ignore. But I haven't found a way to do that other than turn off eslint (via .eslintignore) for the entire
rules.context.schema.yml
file, which I don't want to do.Perhaps instead there's a better way to write the schema if the mapping needs to be extended.
- πΊπΈUnited States tr Cascadia
Also, this issue is not meant to solve the bigger JavaScript issue raised in π Update Rules autocomplete.js to track core changes Active .
- Status changed to Needs review
5 months ago 7:21pm 8 October 2024