Skip to content

Releases: zimicjs/zimic

v0.12.0-canary.3

23 Dec 23:13
Compare
Choose a tag to compare
v0.12.0-canary.3 Pre-release
Pre-release

Chore

Full Changelog: v0.12.0-canary.2...v0.12.0-canary.3

v0.12.0-canary.2

23 Dec 23:05
Compare
Choose a tag to compare
v0.12.0-canary.2 Pre-release
Pre-release

Features

Full Changelog: v0.12.0-canary.1...v0.12.0-canary.2

v0.12.0-canary.1

22 Dec 15:23
Compare
Choose a tag to compare
v0.12.0-canary.1 Pre-release
Pre-release

Features

Full Changelog: v0.12.0-canary.0...v0.12.0-canary.1

v0.12.0-canary.0

22 Dec 14:17
Compare
Choose a tag to compare
v0.12.0-canary.0 Pre-release
Pre-release

Chore

Full Changelog: v0.11.1...v0.12.0-canary.0

v0.11.1

15 Dec 15:06
Compare
Choose a tag to compare

v0.11.1 is here! πŸŽ‰

Dependencies

  • βš™οΈ General dependency upgrades (in f959efb)

Credits

Huge thanks to @diego-aquino for helping!

Full Changelog: v0.11.0...v0.11.1

v0.11.1-canary.0

15 Dec 14:48
Compare
Choose a tag to compare
v0.11.1-canary.0 Pre-release
Pre-release

Chore

Full Changelog: v0.11.0...v0.11.1-canary.0

v0.11.0

08 Dec 15:10
Compare
Choose a tag to compare

v0.11.0 is here! πŸŽ‰

Features

  • πŸ’‘ Improved local unhandled request warnings (#491 in cb123d3):

    Starting in v0.11, Zimic will only warn about local unhandled requests if they have some running interceptor. As of v0.10, any local unhandled requests would be warned by default after starting a local interceptor. This was a common source of confusion because the warnings were not limited to the base URLs of the interceptors and frequently required default unhanded strategies to ignore unrelated or unmocked requests. The confusion was aggravated by this behavior being different from remote interceptors. v0.11 improves the consistency between local and remote interceptors regarding unhandled requests, which are now only warned if they match the base URL of some running interceptor. Learn more at Unhandled requests.

    If you used default unhanded strategies to ignore unrelated or unmocked requests up to v0.10, they are likely no longer necessary!

  • πŸ›‘οΈ Default local unhandled request rejection (#492 in 671703f)

    To further improve consistency between local and remove interceptors, local unhandled requests are now rejected by default, instead of bypassed. To preserve the behavior up to v0.10, you can use action: 'bypass' for your local interceptors. However, we recommend considering and migrating to reject, which prevents unhandled requests from reaching real services and causing false test positives. Learn more at Unhandled requests.

  • βš™οΈ interceptor.clear() now fully clears handlers (#506 in 5fa6969)

    Calling interceptor.clear() now also clears response declarations, restrictions, and intercepted requests from its handlers. Up to v0.10, the handlers had only their response declarations cleared, which was not what the documentation indicated. v0.11 improves the clearing behavior to be more intuitive and work as described in the docs.

Performance

  • ⚑ Improve the typing performance of HTTP interceptors (#502 in 4d910a7)

    v0.11 includes many performance improvements to the HTTP interceptor and HTTP request handler types. They are now more optimized for type checking by the TypeScript compiler.

Fixes

  • πŸ”§ Array search params are now fully logged in unhandled request warnings (#499 in 7ec0a8f)

Deprecations

Credits

Huge thanks to @diego-aquino for helping!

Full Changelog: v0.10.0...v0.11.0

v0.11.0-canary.7

08 Dec 14:07
Compare
Choose a tag to compare
v0.11.0-canary.7 Pre-release
Pre-release

Features

Full Changelog: v0.11.0-canary.6...v0.11.0-canary.7

v0.11.0-canary.6

08 Dec 13:26
Compare
Choose a tag to compare
v0.11.0-canary.6 Pre-release
Pre-release

Performance

Full Changelog: v0.11.0-canary.5...v0.11.0-canary.6

v0.11.0-canary.5

08 Dec 12:32
Compare
Choose a tag to compare
v0.11.0-canary.5 Pre-release
Pre-release

Chore

Full Changelog: v0.11.0-canary.4...v0.11.0-canary.5