Translate maps to sequences in package metadata #2553
Merged
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.
There are multiple map collections on package metadata that originate from sequential entries. This means that the original order of how the data is written and read is lost, which could lead to semantic differences. This PR updates these inconsistent fields to use a new
[]pkg.KeyValue
to express these collections, preserving the order of the values from the source file read.Fields updated:
ConanLockEntry.Options
GolangBinaryBuildinfoEntry.BuildSettings
though the syntax is parsed linearly ultimately it's represented and used as a mapJavaPomProperties.Extra
JavaManifest
(all of it)LinuxKernelModule.Parameters
Ultimately unnecessary to translate to a sequence since the source data is a JSON mapPhpComposerLockEntry
, fieldsRequire
,Provide
,RequireDev
,Suggest
Note: since this updates the package metadata it requires a breaking JSON schema change.
Fixes #2405