Update dependency pointfreeco/swift-custom-dump to v1.1.2 #65
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 PR contains the following updates:
1.0.0
->1.1.2
Release Notes
pointfreeco/swift-custom-dump (pointfreeco/swift-custom-dump)
v1.1.2
Compare Source
What's Changed
New Contributors
Full Changelog: pointfreeco/swift-custom-dump@1.1.1...1.1.2
v1.1.1
Compare Source
What's Changed
Fixed: Filter properties prefixed with
_$
(https://github.com/pointfreeco/swift-custom-dump/pull/100).Macros like
@Observable
can insert properties prefixed by_$
to a structure. Generally these kinds of properties should be thought of as implementation details and should be filtered from the dump.Full Changelog: pointfreeco/swift-custom-dump@1.1.0...1.1.1
v1.1.0
Compare Source
What's Changed
Added:
XCTAssertDifference
for testing changes to values (https://github.com/pointfreeco/swift-custom-dump/pull/51).This function evaluates a given expression before and after a given operation and then compares the results. The comparison is done by invoking the
changes
closure with a mutable version of the initial value, and then asserting that the modifications made match the final value usingXCTAssertNoDifference
.For example, given a very simple counter structure, we can write a test against its incrementing functionality:
If
changes
does not exhaustively describe all changed fields, the assertion will fail.By omitting the operation you can write a "non-exhaustive" assertion against a value by describing just the fields you want to assert against in the
changes
closure:Infrastructure: README updates (thanks @JacksonUtsch, https://github.com/pointfreeco/swift-custom-dump/pull/96).
Infrastructure: Enable Windows CI (thanks @brianmichel, https://github.com/pointfreeco/swift-custom-dump/pull/99).
New Contributors
Full Changelog: pointfreeco/swift-custom-dump@1.0.0...1.1.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.