Add escapable colons in custom keys #151
Merged
Conversation
This file contains 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.
Allows for colon characters as part of the custom key syntax by backslash escaping them.
e.g.
__custom:ns\:parameter:1will resolve to a custom key ofns:parameterI really appreciate how easy this package is making it to build XML for interaction with a partner's SOAP interface Unfortunately, I have encountered a scenario requiring colon-delimited custom keys, which isn't possible (that I know of) using the current explode() approach. This modification would allow more flexibility in the custom key name.
Thank you so much for this and so many other packages, and for considering this PR!