docs: clarify case-sensitive value check for highest-available-docume…#6028
Open
mithilP007 wants to merge 1 commit intowebhintio:mainfrom
Open
docs: clarify case-sensitive value check for highest-available-docume…#6028mithilP007 wants to merge 1 commit intowebhintio:mainfrom
mithilP007 wants to merge 1 commit intowebhintio:mainfrom
Conversation
…nt-mode Fixes webhintio#3506 Added a clear note in the "What does the hint check?" section to inform users that the value check is case-sensitive (ie=edge vs IE=edge). This addresses the confusion mentioned in issue webhintio#3506 where the case-sensitivity requirement was buried in the configuration section and not immediately obvious to users.
|
|
4 tasks
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.
…nt-mode
Fixes #3506
Added a clear note in the "What does the hint check?" section to inform users that the value check is case-sensitive (ie=edge vs IE=edge). This addresses the confusion mentioned in issue #3506 where the case-sensitivity requirement was buried in the configuration section and not immediately obvious to users.
Pull request checklist
Make sure you:
For non-trivial changes, please make sure you also:
Short description of the change(s)