Repair and clean metadata #304
Merged
Conversation
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
…ng the experience for the consumer.
…ncluding some way to iterate over the keys and the new json property.
… are normalized with leading whitespace removed and Description available even if found in the payload.
…iption is available.
|
Technically, this proposed change is a backward-incompatible one. Any projects that are depending on |
f824051 to
c8b753e
Compare
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.
Superseding #301 and #303, update the PackageMetadata protocol thus:
Description(even if found in the payload).jsonproperty that converts the metadata into a JSON-compatible format per PEP 566.Fixes #275, Fixes #276, Fixes #277.