Backport of Configure Ember Data ID Generation into release/1.13.x #19442
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.
Backport
This PR is auto-generated from #19428 to be assessed for backporting due to the inclusion of the label backport/1.13.x.
The below text is copied from the body of the original PR.
Ember Data started using the uuidv4 library for ID generation which uses
crypto.getRandomUUID
which is not available in unsecure contexts. There was a polyfill added in4.6.2
, but until we can upgrade an initializer has been created to configure the id generation method using theuuid
library which was brought in to replacecrypto
in our codebase.More information in this Ember Data issue
Overview of commits