ContainerRegistry: Don't escape slashes in MIME types #143
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.
Motivation
JSONEncoder escapes slashes in strings, so slashes in MIME types written into JSON metadata objects will be escaped. Runtimes seem to accept this, but do not do it when producing images themselves.
Modifications
Add
.withoutEscapingSlashes
to the list of JSONEncoder options.Result
MIME types will not have escaped slashes.
Test Plan
All existing tests continue to pass.