Ensure domains' alphabetical ordering with ESLint rules #39
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
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/jpbulman/only-the-recipe/5KEV8ojyofc8YENvPq7eRzqKpMf5 |
Eldemarkki
changed the title
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.
This change will make sure that all domains are in alphabetical order with the
sort-keysESLint rule. I had to do some changes to the codebase (like remove the bigsupportedDomainsarray) to make it work, and it will probably cause a lot of merge conflicts with the other PRs. However, I think this is much cleaner than duplicating the domain list in 2 places (supportedDomainsandrecipeSelectors).