[Breaking change] Remove internal ponyfills for Map and Set global objects#357
Merged
EmilianoSanchez merged 12 commits intobreaking_changesfrom Oct 18, 2024
Merged
Conversation
…LocalStorage introduced in JavaScript SDK v10.17.3
…affic type to SDK clients
Map, Set and Array.from global objectsMap and Set global objects
gthea
approved these changes
Oct 18, 2024
…ng_changes_remove_deprecated_features
…ed_features [Breaking change] Remove SDK clients with bound traffic type
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
JavaScript commons library
What did you accomplish?
MapandSetinternal ponyfills, dropping support for IE and other outdated browsers. The SDK now requires the runtime environment to support these features natively or to provide a polyfill.eslint-plugin-compatconfiguration.How do we test the changes introduced in this PR?
Extra Notes