Contributor docs: loosen restrictions on caniuse correspondence #1915
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
github-actions
bot
added
the
documentation
jamesnw
approved these changes
Oct 7, 2024
autonome
approved these changes
Oct 8, 2024
Elchi3
approved these changes
Oct 9, 2024
Merged
captainbrosset
approved these changes
Oct 14, 2024
Co-authored-by: Patrick Brosset <patrick.brosset@microsoft.com>
ddbeck
force-pushed
the
caniuse-guideline-looser
branch
from
d42d17c
to
ed46c1f
Compare
captainbrosset
approved these changes
Oct 14, 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.
Right now, we spend quite a lot of time reviewing and correcting discrepancies with caniuse. Only some of those discrepancies are visible to developers (right now), so I'm proposing relaxing the rules such that we care only about:
This change means we will (temporarily) overlook discrepancies for versions that do not affect the overall status or Baseline low date.
In the medium term, we ought to do #1880 and burn down its errors and warnings.
I spoke with @Fyrd today about this idea and got his nod of approval for this approach.