-
Notifications
You must be signed in to change notification settings - Fork 68
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(ses): Provide guidance/coordination for SES incompatibility tracking #1612
Conversation
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.
Love it!
LGTM, thanks!
}); | ||
``` | ||
|
||
Upon encountering an incompatibility, we recommend that you add a comment to |
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.
recommend why?
packages/ses/README.md
Outdated
``` | ||
|
||
Upon encountering an incompatibility, we recommend that you add a comment to | ||
[issue #576][incompatibility tracking] and file an issue with the external project referencing this section. |
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.
we could reduce the load for filing the issue by providing a template. e.g.
Some applications defend themselves by freezing their intrinsics. This project has some assignments or mutations that break in such an environment.
Specifically,
[link to source in the project]Please consider making the project compatible with these environments by avoiding mutations to intrinsics.
If you don't have the capacity but would accept a PR, please comment to that effect so that a volunteer knows their efforts would be welcomed.
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.
Good idea, and thank you for the starting point. PTAL.
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.
I think we can narrow this from "assignment or mutation" to just "assignment".
by avoiding mutations to intrinsics
Is sometimes the issue and should be mentioned when relevant. But by far the most common case is using assignment to override a property inherited from a frozen intrinsic, i.e., the override mistake. We should always lead with the override mistake.
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.
And for the override mistake, always first suggest doing the override by defineProperty
rather than assignment, because that is much more likely to be correctness preserving and least effort.
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.
Or rather defineProperties
since that's what is already shown in this PR's example code.
5c8b136
to
f9c4283
Compare
f9c4283
to
9217767
Compare
Fixes #1611