Repository navigation
Conversation
validate-gts now resolves plugins in .htmlvalidate.json through html-validate's ESM resolver, with <rootDir> as the config's folder. Local plugin files are part of the report cache key. isComponentInvocation(element) tells a custom rule that an element stands in for a component call, so it can skip call sites.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes project-specific rules possible with
validate-gts.validate-gtsloads plugins from.htmlvalidate.json, e.g."<rootDir>/lint/html-rules.mjs". Before, it failed with "Failed to load plugin".isComponentInvocation(element): true when an element stands in for a component call (<Modal>validated as<dialog>). A rule can use it to report in the component's own template only.The README has a "Custom rules" section.
Cowritten by Claude