Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs Bug] Explain severity values #3437

Closed
molant opened this issue Dec 11, 2019 · 2 comments
Closed

[Docs Bug] Explain severity values #3437

molant opened this issue Dec 11, 2019 · 2 comments
Assignees
Labels
agenda area:documentation msft-consider Issues being considered for contributions from Microsoft priority:medium type:bug

Comments

@molant
Copy link
Member

molant commented Dec 11, 2019

We need to document the severity changes somewhere in the docs and probably link from the browser extension and online scanner.

  • Error - Will definitely not work as intended in at least one of the target browsers
  • Warning - Minor impact or may not cause problems in practice (even if technically "wrong")
  • Hint - Fine for now, but could cause problems in the future if something changes
  • Information - Additional context or FYI, possibly to help with other parts of a feature

When configuring hints via .hintrc, the value Default can also be used to let webhint choose the appropriate level (typically when setting a configuration for some other aspect of a hint but wanting to keep the default severity).

@hxlnt hxlnt self-assigned this Feb 28, 2020
@hxlnt hxlnt added the msft-consider Issues being considered for contributions from Microsoft label Feb 28, 2020
@utsavized utsavized changed the title [Docs Bug] Explain severity values [Docs Bug] Explain severity values. Feb 28, 2020
@utsavized utsavized changed the title [Docs Bug] Explain severity values. [Docs Bug] Explain severity values Feb 28, 2020
@antross antross added this to the 2004-1 milestone Mar 27, 2020
@hxlnt hxlnt modified the milestones: 2004-1, 2004-2 Apr 10, 2020
@hxlnt hxlnt modified the milestones: 2004-2, 2005-2 May 8, 2020
@hxlnt hxlnt modified the milestones: 2005-2, 2007-1 Jun 26, 2020
@hxlnt hxlnt assigned hxlnt and unassigned hxlnt Jul 24, 2020
@hxlnt hxlnt modified the milestones: 2007-1, 2008-1 Jul 24, 2020
@hxlnt
Copy link
Member

hxlnt commented Jul 24, 2020

@Reezaali will be working on this one next sprint.

@hxlnt hxlnt added the agenda label Jul 24, 2020
@antross antross removed this from the 2008-1 milestone Oct 30, 2020
@hxlnt
Copy link
Member

hxlnt commented May 12, 2021

I think we fixed this and forgot to link the PR to this issue See https://webhint.io/docs/user-guide/concepts/hints/. @antross @molant, feel free to reopen if this is in error.

@hxlnt hxlnt closed this as completed May 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda area:documentation msft-consider Issues being considered for contributions from Microsoft priority:medium type:bug
Projects
None yet
Development

No branches or pull requests

3 participants