-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Private APIs: remove obsolete try/catch block #65898
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: -54 B (0%) Total Size: 1.77 MB
ℹ️ View Unchanged
|
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.
Looks good, thank you!
6c6c383
to
81e0e6b
Compare
Co-authored-by: jsnajdr <jsnajdr@git.wordpress.org> Co-authored-by: sirreal <jonsurrell@git.wordpress.org>
A little followup to #61486 that removes a
try
/catch
block around code that accessesglobalThis.IS_WORDPRESS_CORE
. This check was needed when the value checked wasprocess.env.IS_WORDPRESS_CORE
, andprocess.env
could possibly be completely undefined in environments like Storybook. ButglobalThis
is pretty much guaranteed to be everywhere. We don't need thetry
/catch
block any more.The
try
/catch
block was originally added in #47229.