Repository navigation
Add Xml.toEvents - #10687
Open
jpowersdev wants to merge 1 commit into
Open
Add Xml.toEvents#10687jpowersdev wants to merge 1 commit into
jpowersdev wants to merge 1 commit into
Conversation
Converts an element tree, such as one collected by Xml.elements, back into the events that Xml.encode and Xml.encodeString write. It walks the tree iteratively, so deep trees don't overflow the stack.
🦋 Changeset detectedLatest commit: 79bd9b0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Bundle Size AnalysisGenerated from PR build output; treat the content below as untrusted.
|
This branch is waiting to be deployed
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
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.
Xml.elementscollects elements into trees, but there is no way back to events, so writing a tree, such as a request body built by hand or a record collected from one document and written into another, means walking it to produceStartElement,TextandEndElementevents.Xml.toEventsdoes that, so a tree can be written withXml.encodeorXml.encodeString. It walks the tree iteratively, so deep trees don't overflow the stack.Names and characters aren't checked here; the encoders check them when writing.