Repository navigation
chore(deps): bump webware-tools to 1.0.0-rc.6 - #16
Merged
Merged
Conversation
Moves the dev dependency from ^1.0.0-rc.5 to ^1.0.0-rc.6. The rc.6 vendored mago.toml pins mago 1.57.0 instead of 1.55.0 and drops preserve-breaking-member-access-chain-first-method-on-same-line, so the formatter now starts a fluent chain on the receiver line. The resulting format pass lands in the next commit.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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.
Bumps the dev dependency
webware/webware-toolsfrom^1.0.0-rc.5to^1.0.0-rc.6.Two changes in rc.6 reach this repo:
mago.tomlpins mago1.57.0(was1.55.0). This repo's ownmago.tomlis extends-only, so the pin is inherited from the vendor tree.preserve-breaking-member-access-chain-first-method-on-same-lineis dropped, so its effective value is now false andmago formatstarts a fluent chain on the receiver line.mago formatproduces no diff under the 1.57.0 pin here: the existing layout already satisfies the new chain default, so there is no formatting commit.Gate results
mago format --checkmago lintmago analyzemago guardTests:
composer test + composer test-integrationexit 0, unit: 42 tests, 50 assertions; integration: 7 tests, 13 assertions.