Define all @upfluence template linting rules in our plugin to be extended by others #458
Conversation
This file contains 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
Base automatically changed from
pn/vel-4518/cleanup-bootstrap-imports-part-1
to
master
December 18, 2024 13:33
phndiaye
force-pushed
the
pn/chore/ember-template-linting
branch
from
967a2a6 to
68366f9
Compare
JulienVannier66
approved these changes
Dec 18, 2024
aprentout
approved these changes
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
This PR updates the internal handlebars linter w/ all rules that are turned-off as we start properly linting our templates. The idea is to gradually enable again the turned-off rules and add custom ones in the future.
What are the observable changes?
Good PR checklist