Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update dependency quick/nimble to v13 - autoclosed #348

Closed
wants to merge 1 commit into from
Closed

chore(deps): update dependency quick/nimble to v13 - autoclosed #348

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 10, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Update Change
Quick/Nimble major 9.2.1 -> 13.2.0

Release Notes

Quick/Nimble (Quick/Nimble)

v13.2.0: - visionOS, map matcher.

Compare Source

Highlights

  • Nimble now supports visionOS! Thanks @​stonko1994!
  • Adds a new map matcher. map allows you to transform the expression to another value, and pass that value to another matcher.
    • For example, if you wanted to match the first element in a tuple easily, you could write: expect(myTuple).to(map(\.0, equal(expectedValue))).
    • See the docs for more suggestions!

Autogenerated Release Notes

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v13.1.2...v13.2.0

v13.1.2

Compare Source

What's Changed

Full Changelog: Quick/Nimble@v13.1.1...v13.1.2

v13.1.1: - The Require DSL, but now with a fixed cocoapods build

Compare Source

Highlights

See the previous release for more on the require DSL.

BugFixes

  • Fix cocoapods release.

Automated Release Notes

What's Changed

Full Changelog: Quick/Nimble@v13.1.0...v13.1.1

v13.1.0: - The Require DSL

Compare Source

Highlights

New Features

  • Introduce the require dsl. This throws an error (a RequireError, or a custom one) if the matcher used with it fails. If the matcher doesn't fail, then the require dsl will return the result of the expression.
    • For example, try require([1, 2, 3]).to(haveCount(3)) will return [1, 2, 3]. However try require(2).toEqual(1)) will throw a RequireError.
    • When the matcher fails, require will still register the assertion failure with XCTest.
    • This also adds unwrap and pollUnwrap, which are work as try require(...).toNot(beNil()) and try require(...).toEventuallyNot(beNil()). With both sync and async variants. They either throw, or return non-optional versions of the expression.
    • See the documentation here for more.

Deprecations

  • Removes Expectation.onFailure, as the new require dsl entirely replaces that API. This deprecation will persist through Nimble 14, before being marked as removed in Nimble 15 and fully removed in Nimble 16.

Breaking Changes

  • The throwAssertion matcher no longer supports watchOS and tvOS in the cocoapods distribution of Nimble. This is because Nimble no longer directly embeds the CwlCatchException CwlPreconditionTesting libraries used in that matcher and instead Nimble pulls in those libraries transitively through the package manager used.

Automated Release Notes

What's Changed

Full Changelog: Quick/Nimble@v13.0.0...v13.1.0

v13.0.0

Compare Source

Highlights

New Features

  • Nimble now supports Windows! (Thanks @​brianmichel!)
  • the Predicate series of APIs has been renamed to Matcher. There are typealiases for the older APIs to better enable migrations. These typealiases will be marked as removed in the next major version of Nimble (Nimble 14), and they will be removed entirely in Nimble 15.
  • Nimble now supports the DriverKit platform.

Breaking Changes

  • The Predicate series of APIs have been renamed.
  • The AsyncDefaults struct is now marked as removed. It will be fully removed in the next major version of Nimble.
  • The platform-independent targets in Nimble.xcodeproj have now been consolidated into a single Nimble (and NimbleTests) target.

Other Notes

Automated Release Notes

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v12.3.0...v13.0.0

v12.3.0

Compare Source

Highlights

  • the async variant of toEventually no longer kicks off unstructured background tasks to check that the matcher matches. This means that there will no longer be the possibility that the same value will be being checked by multiples of the same matcher.

What's Changed

Full Changelog: Quick/Nimble@v12.2.0...v12.3.0

v12.2.0

Compare Source

Highlights

the equal matcher now supports arrays of tuples. For example:

expect([
    (1, 2),
    (3, 4)
]).to(equal([
    (1, 2),
    (3, 4)
]))

Thanks @​faroman for their contribution!

Automatically Generated Release Notes

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v12.1.0...v12.2.0

v12.1.0: - AsyncPredicate

Compare Source

Highlights

  • You can now create Predicates that run in async contexts.

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v12.0.1...v12.1.0

v12.0.1

Compare Source

What's Changed

Full Changelog: Quick/Nimble@v12.0.0...v12.0.1

v12.0.0

Compare Source

Nimble 12 adds the ability to using polling expectations with async expressions. Additionally, Nimble 12 includes a number of quality-of-life improvements and bug fixes.

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v11.2.2...v12.0.0

v11.2.2

Compare Source

Highlights

Nimble v11.2.2 is a minor bug fix release which fixes the build on Xcode 14.3 and Wasm.

Thanks to @​dymv for fixing the Xcode 14.3 build and to @​ikesyo for fixing the wasm build!

Autogenerated Changelog

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v11.2.1...v11.2.2

v11.2.1

Compare Source

Fixed tripping the main thread checker in async toEventually checks. Your CI should no longer report that tests erroneously crashed because the expression's debugDescription dared to reference something that needed to run on the main thread.

What's Changed

Full Changelog: Quick/Nimble@v11.2.0...v11.2.1

v11.2.0

Compare Source

Improved developer experience by allowing you to use the sync form of expect in a test that has other usage of async test. i.e. the following code compiles again:

class MyTest: XCTestCase {
    func testExample() {
        await someAsyncFunction()
        expect(someValue).to(equal(expectedValue))
    }
}

What's Changed

Full Changelog: Quick/Nimble@v11.1.1...v11.2.0

v11.1.1

Compare Source

What's Changed

Full Changelog: Quick/Nimble@v11.1.0...v11.1.1

v11.1.0

Compare Source

11.1.0 drops support for Swift 5.6 (you must use Xcode 14 or later). https://github.com/Quick/Nimble/pull/1009

11.1.0 fixes a developer experience bug where you could unknowingly use the sync version of toEventually in an async context, which will cause test timeout failures. https://github.com/Quick/Nimble/pull/1010

That is, the following test method (XCTest-style) would compile with no errors or warnings emitted, but fail at test runtime due to timeout issues. In v11.1.0, this now emits a warning that you're using the wrong version of toEventually (and similar).

@​MainActor func testSomething() async {
    expect(1).toEventually(equal(1)) // (in v11.0.0, this would not emit any kind of warning or error, but would definitely fail with a timeout error)
}

Full Changelog: Quick/Nimble@v11.0.0...v11.1.0

v11.0.0

Compare Source

This closes the v11.0.0 milestone.

Highlights

Primarily, this release now supports running tests in async contexts.

Fixed

New

Breaking

Auto-generated release notes

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v10.0.0...v11.0.0

v10.0.0

Compare Source

This closes the v10.0.0 milestone.

Highlights

See additional details under the auto-generated release notes below.

Fixed

  • Various documentation improvements
  • Remove various deprecated APIs

New

  • Add toAlways, the inverse of toNever #​969
  • Add beWithin matcher #​886
  • Support nested optionals in beNil matcher #​894
  • Support operator overloads for beNil matcher #​893
  • Support throwAssertion matcher on SwiftPM on Linux #​891
  • Add support for tuples of up to 6 elements to equal matcher, as with the standard library #​880
  • Add matchers for Swift 5 Result type #​643

Breaking

  • Swift 5.4+
  • Xcode 12.5+
  • Remove old Matcher API #​876
  • Use FloatingPoint protocol in beCloseTo matcher #​879
  • passFunc of allPass matcher now takes S.Element over S.Element? #​895

Auto-generated release notes

What's Changed

New Contributors

Full Changelog: Quick/Nimble@v9.2.0...v10.0.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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@techprimate-bot
Copy link

Warnings
⚠️ The Package.swift was updated, but there were no changes in TPPDF.podspec, Package.resolved. Did you forget to update them?

SwiftLint found issues

Severity File Reason
Warning Package.swift:16 There should be no space before and one after any comma. (comma)
Warning Package.swift:5 All declarations should specify Access Control Level keywords explicitly. (explicit_acl)
Warning Package.swift:12 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:16 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:25 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:32 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:33 Collection literals should not have trailing commas. (trailing_comma)

Generated by 🚫 Danger Swift against 29fe04d

@renovate renovate bot force-pushed the renovate/quick-nimble-13.x branch from 29fe04d to 37eabab Compare December 21, 2023 18:42
@techprimate-bot
Copy link

Warnings
⚠️ The Package.swift was updated, but there were no changes in TPPDF.podspec, Package.resolved. Did you forget to update them?

SwiftLint found issues

Severity File Reason
Warning Package.swift:16 There should be no space before and one after any comma. (comma)
Warning Package.swift:5 All declarations should specify Access Control Level keywords explicitly. (explicit_acl)
Warning Package.swift:12 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:16 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:25 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:32 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:33 Collection literals should not have trailing commas. (trailing_comma)

Generated by 🚫 Danger Swift against 37eabab

@renovate renovate bot force-pushed the renovate/quick-nimble-13.x branch from 37eabab to f1ec2ae Compare December 21, 2023 22:18
@techprimate-bot
Copy link

Warnings
⚠️ The Package.swift was updated, but there were no changes in TPPDF.podspec, Package.resolved. Did you forget to update them?

SwiftLint found issues

Severity File Reason
Warning Package.swift:16 There should be no space before and one after any comma. (comma)
Warning Package.swift:5 All declarations should specify Access Control Level keywords explicitly. (explicit_acl)
Warning Package.swift:12 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:16 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:25 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:32 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:33 Collection literals should not have trailing commas. (trailing_comma)

Generated by 🚫 Danger Swift against f1ec2ae

@renovate renovate bot force-pushed the renovate/quick-nimble-13.x branch from f1ec2ae to a22ddba Compare January 5, 2024 06:46
@techprimate-bot
Copy link

Warnings
⚠️ The Package.swift was updated, but there were no changes in TPPDF.podspec, Package.resolved. Did you forget to update them?

SwiftLint found issues

Severity File Reason
Warning Package.swift:16 There should be no space before and one after any comma. (comma)
Warning Package.swift:5 All declarations should specify Access Control Level keywords explicitly. (explicit_acl)
Warning Package.swift:12 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:16 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:25 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:32 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:33 Collection literals should not have trailing commas. (trailing_comma)

Generated by 🚫 Danger Swift against a22ddba

@renovate renovate bot force-pushed the renovate/quick-nimble-13.x branch from a22ddba to e5e0624 Compare January 18, 2024 00:01
@techprimate-bot
Copy link

Warnings
⚠️ The Package.swift was updated, but there were no changes in TPPDF.podspec, Package.resolved. Did you forget to update them?

SwiftLint found issues

Severity File Reason
Warning Package.swift:16 There should be no space before and one after any comma. (comma)
Warning Package.swift:5 All declarations should specify Access Control Level keywords explicitly. (explicit_acl)
Warning Package.swift:12 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:16 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:25 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:32 Collection literals should not have trailing commas. (trailing_comma)
Warning Package.swift:33 Collection literals should not have trailing commas. (trailing_comma)

Generated by 🚫 Danger Swift against e5e0624

@renovate renovate bot changed the title chore(deps): update dependency quick/nimble to v13 chore(deps): update dependency quick/nimble to v13 - autoclosed Feb 19, 2024
@renovate renovate bot closed this Feb 19, 2024
@renovate renovate bot deleted the renovate/quick-nimble-13.x branch February 19, 2024 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@techprimate-bot