-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Remove Autolinker from global scope #8034
Conversation
Resolves CesiumGS#3497 Resolves CesiumGS#7981
Thank you so much for the pull request @ajlende! I noticed this is your first pull request and I wanted to say welcome to the Cesium community! The Pull Request Guidelines is a handy reference for making sure your PR gets accepted quickly, so make sure to skim that.
Reviewers, don't forget to make sure that:
|
I signed the Individual CLA and added myself to CONTRIBUTORS.md |
Thanks @ajlende ! I can confirm we received your CLA. Looks like a pretty straightforward change, hopefully we can get it in in the next release. |
Thanks again for your contribution @ajlende! No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy? I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with |
Thanks for the PR @ajlende! Sorry it took so long to get you a review on this. Instead of modifying the version we have in the repo, can you please update the library to the latest version which you said has a fix for this? Thanks! |
@ajlende thanks again for this PR. Were in the process of migrating Cesium to ES6 modules and Autolinker has been updated to the latest version and fixed as part of that process. It should go into master and be part of the Nov 1 release. |
I'm trying to build Cesium with Webpack and I ran into the same error as #7981.
I'm guessing it has something to do with the bundled code being run in strict mode, but I didn't dive very deep into why Webpack was treating
this
asvoid 0
in the bundle.Either way, this also happens to resolve #3497, and cleans up the global scope.
Autolinker fixed this in v0.24.1, but the bundled version here is 0.17.1, so to keep it safe, I just updated the UMD header.