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.
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
report: add Trust & Safety group under Best Practices #10623
report: add Trust & Safety group under Best Practices #10623
Changes from 7 commits
ec2be2d
2b3d5f0
7494909
e304ec8
ffedbc0
084467f
723352a
593fd59
9d61065
acbb6e4
2237f99
722ff75
7a30125
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe
best-practices-trust-safety
?If I come in looking for the Trust and Safety group, my ctrl-f would definitely start with "trust" :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
best-practices-compat
if we're abbreviating? could also just be more verbose for this onebest-practices-browser-compat
browser feels a bit too vague since all of this in a browser :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
toMatchObject
here only checks that everything inextendedConfig
is inconfig
, which meansconfig
can beextendedConfig
plus extra non-matching properties and this assertion would still pass.e.g. if one of the
gatherer.implementation
inextendedConfig
accidentally got switched to{}
, it would match with almost anything in the samegatherer.implementation
slot inconfig
.This could be checked both ways (each is a subset of the other) with
to check both directions but I think we really want
to make sure we're being strict on equality.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh good catch, while we're on the subject I don't think the message part works with that particular
expect
API, so we can nixhad mutations
or convert it to a comment and stick to the actual object diff