codecov-commenter
commented
3 months ago Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 90.23%. Comparing base (
8c2f76c) to head (9d4a217).
Additional details and impacted files
```diff @@ Coverage Diff @@ ## main #992 +/- ## ======================================= Coverage 90.23% 90.23% ======================================= Files 177 177 Lines 21105 21105 Branches 301 301 ======================================= Hits 19044 19044 Misses 2057 2057 Partials 4 4 ``` | [Flag](https://app.codecov.io/gh/matrix-org/matrix-rich-text-editor/pull/992/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=matrix-org) | Coverage Δ | | |---|---|---| | [uitests](https://app.codecov.io/gh/matrix-org/matrix-rich-text-editor/pull/992/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=matrix-org) | `86.69% <ø> (ø)` | | | [uitests-ios](https://app.codecov.io/gh/matrix-org/matrix-rich-text-editor/pull/992/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=matrix-org) | `86.69% <ø> (ø)` | | | [unittests](https://app.codecov.io/gh/matrix-org/matrix-rich-text-editor/pull/992/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=matrix-org) | `89.34% <ø> (+<0.01%)` | :arrow_up: | | [unittests-ios](https://app.codecov.io/gh/matrix-org/matrix-rich-text-editor/pull/992/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=matrix-org) | `88.76% <ø> (+0.07%)` | :arrow_up: | | [unittests-react](https://app.codecov.io/gh/matrix-org/matrix-rich-text-editor/pull/992/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=matrix-org) | `87.99% <ø> (ø)` | | | [unittests-rust](https://app.codecov.io/gh/matrix-org/matrix-rich-text-editor/pull/992/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=matrix-org) | `89.65% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=matrix-org#carryforward-flags-in-the-pull-request-comment) to find out more.:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
sonarcloud[bot]
This PR contains the following updates:
from: "1.2.0"->from: "1.4.0"from: "1.10.0"->from: "1.16.1"Release Notes
apple/swift-argument-parser (apple/swift-argument-parser)
### [`v1.4.0`](https://togithub.com/apple/swift-argument-parser/blob/HEAD/CHANGELOG.md#140---2024-05-21) [Compare Source](https://togithub.com/apple/swift-argument-parser/compare/1.3.1...1.4.0) ##### Additions - Adds support for subcommand aliases via a new `CommandConfiguration.aliases` parameter. Aliases are shown in help text and used during command parsing. For example, a subcommand like "average" from the example "math" tool can be defined with the aliases `["avg"]`. The resulting subcommand can now be invoked with either of `math stats average` and \`\`math stats avg\`. See the updated documentation and example for additional details. (\[[#627](https://togithub.com/apple/swift-argument-parser/issues/627)]) - Adds a new API `usageString` to `ParsableArguments` and `ParsableCommand` for retrieving their usage text, allowing for more flexible construction of error screens. (\[[#634](https://togithub.com/apple/swift-argument-parser/issues/634)]) - Adds support for passing custom arguments to `AsyncParsableCommand.main()` with a new `static func main(_ arguments: [String]?) async` method. (\[[#568](https://togithub.com/apple/swift-argument-parser/issues/568)]) ##### Fixes - Removes default parameter values from deprecated CommandConfiguration initializers to prevent them from being selected as overloads. Some niche invalid deprecation warnings should no longer occur. (\[[#636](https://togithub.com/apple/swift-argument-parser/issues/636)]) The 1.4.0 release includes contributions from \[Austinpayne], \[dcantah], \[KS1019], \[natecook1000], \[rauhul], and \[revolter]. Thank you! ### [`v1.3.1`](https://togithub.com/apple/swift-argument-parser/blob/HEAD/CHANGELOG.md#131---2024-03-16) [Compare Source](https://togithub.com/apple/swift-argument-parser/compare/1.3.0...1.3.1) ##### Changes - The `CommandConfiguration` type is now designated as `Sendable`. (\[[#615](https://togithub.com/apple/swift-argument-parser/issues/615)]) - The library uses `internal` imports instead of `@_implementationOnly` annotations in Swift versions where permitted. (\[[#616](https://togithub.com/apple/swift-argument-parser/issues/616)]) ##### Fixes - `@Option`- and `@Argument`-annotated optional properties that use a `transform` closure for parsing can now be declared without ambiguity. (\[[#619](https://togithub.com/apple/swift-argument-parser/issues/619)]) - The help flag is now recognized more consistently when a default subcommand has been specified. (\[[#612](https://togithub.com/apple/swift-argument-parser/issues/612)]) - Options that use the `.upToNextOption` parsing strategy can now recognize an attached value (e.g. `--numbers=1 2 3`). (\[[#610](https://togithub.com/apple/swift-argument-parser/issues/610)]) - Generated completion scripts for `zsh` handle repeatable options correctly. (\[[#614](https://togithub.com/apple/swift-argument-parser/issues/614)]) - Documentation improvements and clarifications. (\[[#607](https://togithub.com/apple/swift-argument-parser/issues/607)], \[[#611](https://togithub.com/apple/swift-argument-parser/issues/611)], \[[#617](https://togithub.com/apple/swift-argument-parser/issues/617)], \[[#621](https://togithub.com/apple/swift-argument-parser/issues/621)]) - Build improvements for CMake builds. (\[[#606](https://togithub.com/apple/swift-argument-parser/issues/606)], \[[#608](https://togithub.com/apple/swift-argument-parser/issues/608)]) The 1.3.1 release includes contributions from \[Coeur], \[compnerd], \[keith], \[MaxDesiatov], \[mayoff], and \[natecook1000]. Thank you! ### [`v1.3.0`](https://togithub.com/apple/swift-argument-parser/blob/HEAD/CHANGELOG.md#130---2023-12-06) [Compare Source](https://togithub.com/apple/swift-argument-parser/compare/1.2.3...1.3.0) ##### Changes - The `@Option`, `@Argument`, `@Flag`, and `@OptionGroup` property wrappers now conditionally conform to `Sendable` when the wrapper's `Value` type conforms. With this change, you can mark `ParsableCommand` types as `Sendable` when you want to be able to pass a parsed command across concurrent contexts. (\[[#582](https://togithub.com/apple/swift-argument-parser/issues/582)]) *Migration:* Users that aren't ready to resolve sendability warnings can add the `@preconcurrency` attribute to `import ArgumentParser` statements. As part of this update, changes to the `CommandLine.arguments` array before a command's `main` or `parse...` methods are called are no longer observed. Instead of making changes to `CommandLine.arguments`, pass an updated array of arguments to the command's method. - To support migration to `Sendable` annotation, the minimum Swift version for `swift-argument-parser` has been increased to Swift 5.7. Users of older Swift versions will be able to continue using version 1.2.3 of the library. (\[[#582](https://togithub.com/apple/swift-argument-parser/issues/582)]) ##### Additions - Help screens now include possible options for `ExpressibleByArgument` types with non empty `allValueStrings`. Types also conforming to `CaseIterable` do not need to manually implement `allValueStrings`, instead it is derived from `allCases`. (\[[#594](https://togithub.com/apple/swift-argument-parser/issues/594)]) ##### Fixes - The titles for nested option groups are preserved when embedded into commands without specifying a new title. (\[[#592](https://togithub.com/apple/swift-argument-parser/issues/592)]) - When wrapping help and error messages, the library now uses the `COLUMNS` environment variable when set, instead of immediately falling back to 80 columns. (\[[#596](https://togithub.com/apple/swift-argument-parser/issues/596)]) - Bash completion scripts now respect the extensions given in a `.file(...)` completion kind. (\[[#590](https://togithub.com/apple/swift-argument-parser/issues/590)]) - Bash completion scripts now properly escape command names that include hyphens. (\[[#573](https://togithub.com/apple/swift-argument-parser/issues/573)]) - Documentation improvements. (\[[#572](https://togithub.com/apple/swift-argument-parser/issues/572)], \[[#565](https://togithub.com/apple/swift-argument-parser/issues/565)], \[[#602](https://togithub.com/apple/swift-argument-parser/issues/602)]) The 1.3.0 release includes contributions from \[Alkenso], \[compnerd], \[gwynne], \[kennyyork], \[natecook1000], \[rauhul], \[robertmryan], and \[vlm]. Thank you! *** ### [`v1.2.3`](https://togithub.com/apple/swift-argument-parser/blob/HEAD/CHANGELOG.md#123---2023-08-15) [Compare Source](https://togithub.com/apple/swift-argument-parser/compare/1.2.2...1.2.3) ##### Additions - You can now use ArgumentParser with Musl libc. (\[[#574](https://togithub.com/apple/swift-argument-parser/issues/574)]) ##### Fixes - Fixes a bug where single-page manuals did not include command abstracts for subcommands. (\[[#552](https://togithub.com/apple/swift-argument-parser/issues/552)]) - Fixes a bug where non-optional properties in ParsableCommands could cause ArgumentParser to crash. You can now include properties like dictionaries in ParsableCommands without issue. (\[[#554](https://togithub.com/apple/swift-argument-parser/issues/554)]) - Fixes a configuration issue which would cause `ArgumentParserTestHelpers` to fail to link when building for Windows. (\[[#579](https://togithub.com/apple/swift-argument-parser/issues/579)]) The 1.2.3 release includes contributions from \[compnerd], \[gwynne], \[MaxDesiatov], \[natecook1000], and \[rauhul]. Thank you! ### [`v1.2.2`](https://togithub.com/apple/swift-argument-parser/blob/HEAD/CHANGELOG.md#122---2023-02-09) [Compare Source](https://togithub.com/apple/swift-argument-parser/compare/1.2.1...1.2.2) ##### Fixes - Arguments with the `.allUnrecognized` parsing strategy no longer consume built-in flags like `--help` and `--version`. (\[[#550](https://togithub.com/apple/swift-argument-parser/issues/550)]) - Fixes an issue introduced in version 1.2.0 where properties with underscored names couldn't be parsed. (\[[#548](https://togithub.com/apple/swift-argument-parser/issues/548)]) - Improves the error message for cases where platform availability causes the synchronous `ParsableCommand.main()` static method to be run on an `AsyncParsableCommand` type. (\[[#547](https://togithub.com/apple/swift-argument-parser/issues/547)]) ### [`v1.2.1`](https://togithub.com/apple/swift-argument-parser/blob/HEAD/CHANGELOG.md#121---2023-01-12) [Compare Source](https://togithub.com/apple/swift-argument-parser/compare/1.2.0...1.2.1) ##### Changes - Documentation is now primarily hosted at the [Swift Package Index](https://swiftpackageindex.com/apple/swift-argument-parser). ##### Fixes - `exit(_:)` no longer causes infinite recursion on the WASI platform. (\[[#520](https://togithub.com/apple/swift-argument-parser/issues/520)]) - Completion scripts for `fish` now provide completions after a non-hyphen-prefixed argument has been provided. (\[[#535](https://togithub.com/apple/swift-argument-parser/issues/535)]) - Overload selection for custom `ExpressibleByArgument` types has been improved. (\[[#522](https://togithub.com/apple/swift-argument-parser/issues/522)]) - The usage string for `.postTerminator` arguments now includes the required terminator (`--`). (\[[#542](https://togithub.com/apple/swift-argument-parser/issues/542)]) - Documentation and testing fixes and improvements. The 1.2.1 release includes contributions from \[Chamepp], \[kkk669], \[mtj0928], \[natecook1000], \[rauhul], \[rickrizzo], \[TiagoMaiaL], and \[yim-lee]. Thank you!pointfreeco/swift-snapshot-testing (pointfreeco/swift-snapshot-testing)
### [`v1.16.1`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.16.1) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.16.0...1.16.1) #### What's Changed - Fixed: Support swift-syntax from 600.0.0-latest ([https://github.com/pointfreeco/swift-snapshot-testing/pull/858](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/858)). - Fixed: Make `ViewImageConfig` sendable (thanks [@Mika5652](https://togithub.com/Mika5652), [https://github.com/pointfreeco/swift-snapshot-testing/pull/850](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/850)). - Infrastructure: Add README link to SnapshotVision plugin (thanks [@gregersson](https://togithub.com/gregersson), [https://github.com/pointfreeco/swift-snapshot-testing/pull/848](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/848)). #### New Contributors - [@gregersson](https://togithub.com/gregersson) made their first contribution in [https://github.com/pointfreeco/swift-snapshot-testing/pull/848](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/848) - [@Mika5652](https://togithub.com/Mika5652) made their first contribution in [https://github.com/pointfreeco/swift-snapshot-testing/pull/850](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/850) **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.16.0...1.16.1 ### [`v1.16.0`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.16.0) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.15.4...1.16.0) #### What's Changed - Added: Inline snapshots can now be removed programmatically ([https://github.com/pointfreeco/swift-snapshot-testing/pull/844](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/844)). - Fixed: Test observer is now forced to register on the main queue (thanks [@MarkVillacampa](https://togithub.com/MarkVillacampa), [https://github.com/pointfreeco/swift-snapshot-testing/pull/834](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/834)). #### New Contributors - [@MarkVillacampa](https://togithub.com/MarkVillacampa) made their first contribution in [https://github.com/pointfreeco/swift-snapshot-testing/pull/834](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/834) **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.15.4...1.16.0 ### [`v1.15.4`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.15.4) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.15.3...1.15.4) #### What's Changed - Fixed: Bump swift-syntax requirements to support 5.10.0 ([https://github.com/pointfreeco/swift-snapshot-testing/pull/836](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/836)). **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.15.3...1.15.4 ### [`v1.15.3`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.15.3) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.15.2...1.15.3) #### What's Changed - Fixed: Inline snapshots in test files containing a leading, whitespace-only line will no longer include this newline as leading trivia in the recording. **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.15.2...1.15.3 ### [`v1.15.2`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.15.2) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.15.1...1.15.2) #### What's Changed - Fixed: Support perceptual comparisons on platforms that do not support metal (thanks [@ejensen](https://togithub.com/ejensen), [https://github.com/pointfreeco/swift-snapshot-testing/pull/666](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/666)). - Fixed: Better support for `WKWebView` in Xcode 14 and Xcode 15 (thanks [@teameh](https://togithub.com/teameh), [https://github.com/pointfreeco/swift-snapshot-testing/pull/692](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/692)). **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.15.1...1.15.2 ### [`v1.15.1`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.15.1) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.15.0...1.15.1) #### What's Changed - Improve the speed of comparing memory buffers by [@ejensen](https://togithub.com/ejensen) in [#664](https://togithub.com/pointfreeco/swift-snapshot-testing/issues/664) **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.15.0...1.15.1 ### [`v1.15.0`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.15.0) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.14.2...1.15.0) #### What's Changed - Added: `assertInlineSnapshot` now has `record` mode ([https://github.com/pointfreeco/swift-snapshot-testing/pull/809](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/809)). - Fixed: `assertInlineSnapshot`'s failure difference now reads more correctly as the patch that would be applied were record mode to be on ([https://github.com/pointfreeco/swift-snapshot-testing/pull/809](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/809)). **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.14.2...1.15.0 ### [`v1.14.2`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.14.2) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.14.1...1.14.2) #### What's Changed - Fixed: Inline snapshots are now prepared *before* emitting an XCTest failure, ensuring the artifact is written ([https://github.com/pointfreeco/swift-snapshot-testing/pull/787](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/787)). - Fixed: `assertCustomInline()` no longer leaves empty parens hanging around when expanded ([https://github.com/pointfreeco/swift-snapshot-testing/pull/788](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/788)). - Fixed: The `swift-syntax` dependency has widened to support 508.0.1..<510.0.0, allowing the library to be depended on even when another package depends on 508.0.1 ([https://github.com/pointfreeco/swift-snapshot-testing/pull/795](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/795)). - Infrastructure: Updated SPI configuration for watchOS (thanks [@finestructure](https://togithub.com/finestructure), [https://github.com/pointfreeco/swift-snapshot-testing/pull/789](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/789)). **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.14.1...1.14.2 ### [`v1.14.1`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.14.1) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.14.0...1.14.1) #### What's Changed - Fixed: Avoid inline snapshot trailing closure index crash ([https://github.com/pointfreeco/swift-snapshot-testing/pull/786](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/786)). - Infrastructure: Update .spi.yml to show watchOS support (thanks [@finestructure](https://togithub.com/finestructure), [https://github.com/pointfreeco/swift-snapshot-testing/pull/785](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/785)). **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.14.0...1.14.1 ### [`v1.14.0`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.14.0) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.13.0...1.14.0) #### What's Changed - Added: Support for inline snapshot API migrations ([https://github.com/pointfreeco/swift-snapshot-testing/pull/779](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/779)) - Updated: Pinned SwiftSyntax to 509.0.0 ([https://github.com/pointfreeco/swift-snapshot-testing/pull/774](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/774)). - Fixed: Escape carriage returns explicitly in inline snapshots ([https://github.com/pointfreeco/swift-snapshot-testing/pull/772](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/772)). - Infrastructure: CONTRIBUTING.md fixes (thanks [@soo941226](https://togithub.com/soo941226), [https://github.com/pointfreeco/swift-snapshot-testing/pull/773](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/773)). #### New Contributors - [@soo941226](https://togithub.com/soo941226) made their first contribution in [https://github.com/pointfreeco/swift-snapshot-testing/pull/773](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/773) **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.13.0...1.14.0 ### [`v1.13.0`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.13.0) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.12.0...1.13.0) #### What's Changed - Added: *Inline* Snapshot Testing ([https://github.com/pointfreeco/swift-snapshot-testing/pull/764](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/764)). This allows your text-based snapshots to live right in the test source code, rather than in an external file:  While the library has had experimental support for this feature since [1.5.0](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/1.5.0) thanks to [@rjchatfield](https://togithub.com/rjchatfield) ([https://github.com/pointfreeco/swift-snapshot-testing/pull/199](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/199)), we've finally put the finishing touches to it: - Inline snapshot testing is available in a separate `InlineSnapshotTesting` module. To use inline snapshot testing, add a dependency on this module and update your existing imports: ```diff -import SnapshotTesting +import InlineSnapshotTesting ``` The feature has been rewritten to use [SwiftSyntax](https://togithub.com/apple/swift-syntax). While a heavyweight dependency, it is a more reasonable tool for generating Swift code than string substitution, and will be an increasingly common dependency as the de facto tool for writing Swift macros. The main `SnapshotTesting` module does not depend on SwiftSyntax, so existing snapshot tests will not incur cost of compiling SwiftSyntax. - The API now follows the same structure as `assertSnapshot`, except it uses a trailing closure to capture the inline snapshot. This makes it easy to update an existing snapshot test to use inline snapshots: ```diff -assertSnapshot(of: user, as: .json) +assertInlineSnapshot(of: user, as .json) ``` After this assertion runs, the test source code is updated in place: ```swift assertInlineSnapshot(of: user, as: .json) { """ { "id" : 42, "isAdmin" : true, "name" : "Blob" } """ } ``` These trailing closures are easy to select in Xcode in order to delete and re-record a snapshot: simply double-click one of the braces to highlight the closure, delete, and run the test. - Inline snapshotting's `assertInlineSnapshot` testing tool is fully customizable so that you can build your own testing helpers on top of it without your users even knowing they are using snapshot testing. In fact, we do this to create a testing tool that helps us test the Swift code that powers [Point-Free](https://www.pointfree.co). It's called [`assertRequest`][assert-request-gh], and it allows you to simultaneously assert the request being made to the server (including URL, query parameters, headers, POST body) as well as the response from the server (including status code and headers). For example, to test that when a request is made for a user to join a team subscription, we can [write the following][assert-request-example]: ```swift await assertRequest( connection( from: request( to: .teamInviteCode(.join(code: subscription.teamInviteCode, email: nil)), session: .loggedIn(as: currentUser) ) ) ) ``` And when we first run the test it will automatically [expand][assert-request-example]: ```swift await assertRequest( connection( from: request( to: .teamInviteCode(.join(code: subscription.teamInviteCode, email: nil)), session: .loggedIn(as: currentUser) ) ) ) { """ POST http://localhost:8080/join/subscriptions-team_invite_code3 Cookie: pf_session={"userId":"00000000-0000-0000-0000-000000000001"} """ } response: { """ 302 Found Location: /account Referrer-Policy: strict-origin-when-cross-origin Set-Cookie: pf_session={"flash":{"message":"You now have access to Point-Free!","priority":"notice"},"userId":"00000000-0000-0000-0000-000000000001"}; Expires=Sat, 29 Jan 2028 00:00:00 GMT; Path=/ X-Content-Type-Options: nosniff X-Download-Options: noopen X-Frame-Options: SAMEORIGIN X-Permitted-Cross-Domain-Policies: none X-XSS-Protection: 1; mode=block """ } ``` This shows that the response redirects the use back to their account page and shows them the flash message that they now have full access to Point-Free. This makes writing complex and nuanced tests incredibly easy, and so there is no reason to not write lots of tests for all the subtle edge cases of your application's logic. - Added: DocC documentation ([#765](https://togithub.com/pointfreeco/swift-snapshot-testing/issues/765)). The `SnapshotTesting` and `InlineSnapshotTesting` are fully documented using DocC. - Infrastructure: swift-format support ([#765](https://togithub.com/pointfreeco/swift-snapshot-testing/issues/765)). The library is now auto-formatted using swift-format. **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.12.0...0.13.0 [assert-request-gh]: https://togithub.com/pointfreeco/pointfreeco/blob/5b5cd26d8240bd0e1afb77b7ef342458592c7366/Sources/PointFreeTestSupport/PointFreeTestSupport.swift#L42-L87 [assert-request-example]: https://togithub.com/pointfreeco/pointfreeco/blob/a237ce693258b363ebfb4bdffe6025cc28ac891f/Tests/PointFreeTests/JoinMiddlewareTests.swift#L285-L309 ### [`v1.12.0`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.12.0) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.11.1...1.12.0) #### What's Changed - Added: `assertSnapshot(of:)` is now the default interface for snapshot assertions ([https://github.com/pointfreeco/swift-snapshot-testing/pull/762](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/762)). `assertSnapshot(matching:)` will remain in 1.x as a soft-deprecated alias. - Infrastructure: Add to README plug-ins (thanks [@BarredEwe](https://togithub.com/BarredEwe), [https://github.com/pointfreeco/swift-snapshot-testing/pull/746](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/746); [@tahirmt](https://togithub.com/tahirmt), [https://github.com/pointfreeco/swift-snapshot-testing/pull/763](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/763)). - Infrastructure: Don't ignore Package.resolved ([https://github.com/pointfreeco/swift-snapshot-testing/pull/649](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/649)). #### New Contributors - [@BarredEwe](https://togithub.com/BarredEwe) made their first contribution in [https://github.com/pointfreeco/swift-snapshot-testing/pull/746](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/746) **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.11.1...1.12.0 ### [`v1.11.1`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.11.1) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.11.0...1.11.1) #### What's Changed - Fixed: Xcode 15 support (thanks [@finestructure](https://togithub.com/finestructure), [https://github.com/pointfreeco/swift-snapshot-testing/pull/737](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/737)). - Infrastructure: Add PreviewSnapshots to README "Plug-ins" (thanks [@jflan-dd](https://togithub.com/jflan-dd), [https://github.com/pointfreeco/swift-snapshot-testing/pull/696](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/696)) **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.11.0...1.11.1 ### [`v1.11.0`](https://togithub.com/pointfreeco/swift-snapshot-testing/releases/tag/1.11.0) [Compare Source](https://togithub.com/pointfreeco/swift-snapshot-testing/compare/1.10.0...1.11.0) #### What's Changed - Added: Image paths in Xcode XCTest output are now clickable (thanks [@RufusMall](https://togithub.com/RufusMall), [https://github.com/pointfreeco/swift-snapshot-testing/pull/675](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/675)). - Fixed: Silenced SPM warnings by excluding snapshots and fixtures in Package manifest (thanks [@valeriyvan](https://togithub.com/valeriyvan), [https://github.com/pointfreeco/swift-snapshot-testing/pull/684](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/684)). - Fixed: 1.10.0 erroneously bumped platform requirements. This release reverts compatibility to align with previous versions ([https://github.com/pointfreeco/swift-snapshot-testing/pull/698](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/698)). - Infrastructure: Fixed Ubuntu CI by locking version ([https://github.com/pointfreeco/swift-snapshot-testing/pull/685](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/685)). #### New Contributors - [@RufusMall](https://togithub.com/RufusMall) made their first contribution in [https://github.com/pointfreeco/swift-snapshot-testing/pull/675](https://togithub.com/pointfreeco/swift-snapshot-testing/pull/675) **Full Changelog**: https://github.com/pointfreeco/swift-snapshot-testing/compare/1.10.0...1.11.0Configuration
📅 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.