Refactor package metadata #7
Open
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
codedmonkey
force-pushed
the
package-metadata
branch
from
d20a892 to
09bd57a
Compare
Start of refactoring package metadata by separating package metadata from the version table to a new metadata table to create immutable packages Signed-off-by: Tim Goudriaan <tim@codedmonkey.com>
Signed-off-by: Tim Goudriaan <tim@codedmonkey.com>
…age-related entities Signed-off-by: Tim Goudriaan <tim@codedmonkey.com>
Signed-off-by: Tim Goudriaan <tim@codedmonkey.com>
Signed-off-by: Tim Goudriaan <tim@codedmonkey.com>
Signed-off-by: Tim Goudriaan <tim@codedmonkey.com>
codedmonkey
force-pushed
the
package-metadata
branch
from
09bd57a to
881a671
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.
Re-organizes package metadata to separate Doctrine entities from package versions.
Why?
Since Composer packages are mutable configurations stored per versions, developers can publish new development versions under the same name. However, this is also true for tagged versions.
When fetching a package there is currently no way of knowing what you’re going to receive or if it’s the same as the day before. This is inherit to Composer which simply resolves package metadata directly from a VCS repository. This makes Composer very versatile as you can fetch the package metadata from different sources, but comes at the price of increased attack vectors from the source.