Normalise extension requirements#1185
Merged
localheinz merged 1 commit intoergebnis:mainfrom Apr 10, 2025
Merged
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1185 +/- ##
============================================
+ Coverage 97.33% 97.37% +0.03%
- Complexity 210 216 +6
============================================
Files 32 32
Lines 863 876 +13
============================================
+ Hits 840 853 +13
Misses 23 23 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
021177e to
b2c0dac
Compare
b2c0dac to
2697978
Compare
localheinz
approved these changes
Apr 10, 2025
Member
|
Thank you, @fredden! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This pull request adds normalisation for
ext-*requirements, to match what Composer does internally. I chose to join any collisions with an 'or' separator.Related to ergebnis/composer-normalize#1388