JSONPath with dot notation generator for golang

Build Status Goreport License MIT

jsonpath - Json generation by dot notation

This library is very close to mongodb's dot notation with a bit of extensions.

Supported syntaxes

Standard dot notation

input hash value output json result
{"0.value":"100"} [{"value":"100"}]
{"1.value":"100"} [null, {"value":"100"}]
{"value":"100"} {"value":"100"}
{"value.1":"100"} {"value":[null, "100"]}
{"v.0.k":"100"} {"v":[{"k":100}]}

Extended

input hash value output json result
{"v.num()":"1.0"} {"v":1.0}
{"v.bool()":"true"} {"v":true}

Benchmarks

Run benchmarks

go test -bench=.

Results

v0.0.3

BenchmarkComplexJSONPathArray-8             	  100000	     12480 ns/op
BenchmarkSimpleJSONPathArrayWithNum-8       	  500000	      2654 ns/op
BenchmarkSimpleJSONPathArrayWithBool-8      	 1000000	      2319 ns/op
BenchmarkSimpleJSONPathArrayInsideArray-8   	  500000	      3066 ns/op
BenchmarkSimpleJSONPathArrays-8             	  500000	      2636 ns/op
BenchmarkSimpleJSONPathSimple-8             	 1000000	      1626 ns/op
BenchmarkJSONNative-8                       	 2000000	       959 ns/op

Installation

go get github.com/cthulhu/jsonpath

Usage

in := map[string]string{"0.value": "100.00"}
jsobBytes := jsonpath.Marshal(in)

For more examples check jsonpath_test.go file

LICENSE

See LICENSE file

Owner
Stanislav O. Pogrebnyak
Stanislav O. Pogrebnyak
Comments
  • Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.6.0

    Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.6.0

    Bumps github.com/onsi/ginkgo/v2 from 2.2.0 to 2.6.0.

    Release notes

    Sourced from github.com/onsi/ginkgo/v2's releases.

    v2.6.0

    2.6.0

    Features

    • ReportBeforeSuite provides access to the suite report before the suite begins.
    • Add junit config option for omitting leafnodetype (#1088) [956e6d2]
    • Add support to customize junit report config to omit spec labels (#1087) [de44005]

    Fixes

    • Fix stack trace pruning so that it has a chance of working on windows [2165648]

    v2.5.1

    2.5.1

    Fixes

    • skipped tests only show as 'S' when running with -v [3ab38ae]
    • Fix typo in docs/index.md (#1082) [55fc58d]
    • Fix typo in docs/index.md (#1081) [8a14f1f]
    • Fix link notation in docs/index.md (#1080) [2669612]
    • Fix typo in --progress deprecation message (#1076) [b4b7edc]

    Maintenance

    • chore: Included githubactions in the dependabot config (#976) [baea341]
    • Bump golang.org/x/sys from 0.1.0 to 0.2.0 (#1075) [9646297]

    v2.5.0

    2.5.0

    Ginkgo output now includes a timeline-view of the spec

    This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

    The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node > Enter and < Exit events in the spec timeline.

    In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)

    Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you may run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.

    Features

    ... (truncated)

    Changelog

    Sourced from github.com/onsi/ginkgo/v2's changelog.

    2.6.0

    Features

    • ReportBeforeSuite provides access to the suite report before the suite begins.
    • Add junit config option for omitting leafnodetype (#1088) [956e6d2]
    • Add support to customize junit report config to omit spec labels (#1087) [de44005]

    Fixes

    • Fix stack trace pruning so that it has a chance of working on windows [2165648]

    2.5.1

    Fixes

    • skipped tests only show as 'S' when running with -v [3ab38ae]
    • Fix typo in docs/index.md (#1082) [55fc58d]
    • Fix typo in docs/index.md (#1081) [8a14f1f]
    • Fix link notation in docs/index.md (#1080) [2669612]
    • Fix typo in --progress deprecation message (#1076) [b4b7edc]

    Maintenance

    • chore: Included githubactions in the dependabot config (#976) [baea341]
    • Bump golang.org/x/sys from 0.1.0 to 0.2.0 (#1075) [9646297]

    2.5.0

    Ginkgo output now includes a timeline-view of the spec

    This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

    The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node > Enter and < Exit events in the spec timeline.

    In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)

    Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you may run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.

    Features

    • Provide details about which timeout expired [0f2fa27]

    Fixes

    ... (truncated)

    Commits
    • 6ad4fae v2.6.0
    • 366815d fix race in internal integration spec
    • 1869212 Refactor and clean up ReportBeforeSuite additions.
    • 52b4b9c ReportBeforeSuite provides the suite report before the suite begins
    • 2165648 Fix stack trace pruning so that it has a chance of working on windows
    • 956e6d2 Add junit config option for omitting leafnodetype (#1088)
    • 8804859 Fix typo in docs (#1089)
    • de44005 Add support to customize junit report config to omit spec labels (#1087)
    • a3eed17 v2.5.1
    • 3ab38ae skipped tests only show as 'S' when running with -v
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.5.1

    Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.5.1

    Bumps github.com/onsi/ginkgo/v2 from 2.2.0 to 2.5.1.

    Release notes

    Sourced from github.com/onsi/ginkgo/v2's releases.

    v2.5.1

    2.5.1

    Fixes

    • skipped tests only show as 'S' when running with -v [3ab38ae]
    • Fix typo in docs/index.md (#1082) [55fc58d]
    • Fix typo in docs/index.md (#1081) [8a14f1f]
    • Fix link notation in docs/index.md (#1080) [2669612]
    • Fix typo in --progress deprecation message (#1076) [b4b7edc]

    Maintenance

    • chore: Included githubactions in the dependabot config (#976) [baea341]
    • Bump golang.org/x/sys from 0.1.0 to 0.2.0 (#1075) [9646297]

    v2.5.0

    2.5.0

    Ginkgo output now includes a timeline-view of the spec

    This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

    The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node > Enter and < Exit events in the spec timeline.

    In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)

    Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you may run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.

    Features

    • Provide details about which timeout expired [0f2fa27]

    Fixes

    • Add Support Policy to docs [c70867a]

    Maintenance

    • Bump github.com/onsi/gomega from 1.22.1 to 1.23.0 (#1070) [bb3b4e2]

    v2.4.0

    2.4.0

    ... (truncated)

    Changelog

    Sourced from github.com/onsi/ginkgo/v2's changelog.

    2.5.1

    Fixes

    • skipped tests only show as 'S' when running with -v [3ab38ae]
    • Fix typo in docs/index.md (#1082) [55fc58d]
    • Fix typo in docs/index.md (#1081) [8a14f1f]
    • Fix link notation in docs/index.md (#1080) [2669612]
    • Fix typo in --progress deprecation message (#1076) [b4b7edc]

    Maintenance

    • chore: Included githubactions in the dependabot config (#976) [baea341]
    • Bump golang.org/x/sys from 0.1.0 to 0.2.0 (#1075) [9646297]

    2.5.0

    Ginkgo output now includes a timeline-view of the spec

    This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

    The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node > Enter and < Exit events in the spec timeline.

    In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)

    Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you may run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.

    Features

    • Provide details about which timeout expired [0f2fa27]

    Fixes

    • Add Support Policy to docs [c70867a]

    Maintenance

    • Bump github.com/onsi/gomega from 1.22.1 to 1.23.0 (#1070) [bb3b4e2]

    2.4.0

    Features

    • DeferCleanup supports functions with multiple-return values [5e33c75]

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/gomega from 1.21.1 to 1.24.1

    Bump github.com/onsi/gomega from 1.21.1 to 1.24.1

    Bumps github.com/onsi/gomega from 1.21.1 to 1.24.1.

    Release notes

    Sourced from github.com/onsi/gomega's releases.

    v1.24.1

    No release notes provided.

    v1.24.0

    1.24.0

    Features

    Introducting gcustom - a convenient mechanism for building custom matchers.

    This is an RC release for gcustom. The external API may be tweaked in response to feedback however it is expected to remain mostly stable.

    Maintenance

    • Update BeComparableTo documentation [756eaa0]

    v1.23.0

    1.23.0

    Features

    • Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

    • Substantial improvement have been made to StopTrying():

      • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
      • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
      • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.
    • TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

    • ctx can now be passed-in as the first argument to Eventually and Consistently.

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.3.0 to 2.3.1 (#597) [afed901]
    • Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#599) [7c691b3]
    • Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#587) [ff22665]

    v1.22.1

    1.22.1

    Fixes

    • When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
    • Allow StopTrying() to be wrapped [bf3cba9]

    Maintenance

    • bump to ginkgo v2.3.0 [c5d5c39]

    v1.22.0

    1.22.0

    ... (truncated)

    Changelog

    Sourced from github.com/onsi/gomega's changelog.

    1.24.1

    Fixes

    • maintain backward compatibility for Eventually and Consisntetly's signatures [4c7df5e]
    • fix small typo (#601) [ea0ebe6]

    Maintenance

    • Bump golang.org/x/net from 0.1.0 to 0.2.0 (#603) [1ba8372]
    • Bump github.com/onsi/ginkgo/v2 from 2.4.0 to 2.5.0 (#602) [f9426cb]
    • fix label-filter in test.yml [d795db6]
    • stop running flakey tests and rely on external network dependencies in CI [7133290]

    1.24.0

    Features

    Introducting gcustom - a convenient mechanism for building custom matchers.

    This is an RC release for gcustom. The external API may be tweaked in response to feedback however it is expected to remain mostly stable.

    Maintenance

    • Update BeComparableTo documentation [756eaa0]

    1.23.0

    Features

    • Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

    • Substantial improvement have been made to StopTrying():

      • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
      • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
      • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.
    • TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

    • ctx can now be passed-in as the first argument to Eventually and Consistently.

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.3.0 to 2.3.1 (#597) [afed901]
    • Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#599) [7c691b3]
    • Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#587) [ff22665]

    1.22.1

    Fixes

    • When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
    • Allow StopTrying() to be wrapped [bf3cba9]

    ... (truncated)

    Commits
    • 3eef0d7 v1.24.1
    • 4c7df5e maintain backward compatibility for Eventually and Consisntetly's signatures
    • 1ba8372 Bump golang.org/x/net from 0.1.0 to 0.2.0 (#603)
    • f9426cb Bump github.com/onsi/ginkgo/v2 from 2.4.0 to 2.5.0 (#602)
    • ea0ebe6 fix small typo (#601)
    • d795db6 fix label-filter in test.yml
    • 7133290 stop running flakey tests and rely on external network dependencies in CI
    • ed1156b v1.24.0
    • 756eaa0 Update BeComparableTo documentation
    • 6015576 finish documenting gcustom
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.5.0

    Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.5.0

    Bumps github.com/onsi/ginkgo/v2 from 2.2.0 to 2.5.0.

    Release notes

    Sourced from github.com/onsi/ginkgo/v2's releases.

    v2.5.0

    2.5.0

    Ginkgo output now includes a timeline-view of the spec

    This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

    The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node > Enter and < Exit events in the spec timeline.

    In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)

    Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you may run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.

    Features

    • Provide details about which timeout expired [0f2fa27]

    Fixes

    • Add Support Policy to docs [c70867a]

    Maintenance

    • Bump github.com/onsi/gomega from 1.22.1 to 1.23.0 (#1070) [bb3b4e2]

    v2.4.0

    2.4.0

    Features

    • DeferCleanup supports functions with multiple-return values [5e33c75]
    • Add GinkgoLogr (#1067) [bf78c28]
    • Introduction of 'MustPassRepeatedly' decorator (#1051) [047c02f]

    Fixes

    • correcting some typos (#1064) [1403d3c]
    • fix flaky internal_integration interupt specs [2105ba3]
    • Correct busted link in README [be6b5b9]

    Maintenance

    • Bump actions/checkout from 2 to 3 (#1062) [8a2f483]
    • Bump golang.org/x/tools from 0.1.12 to 0.2.0 (#1065) [529c4e8]

    ... (truncated)

    Changelog

    Sourced from github.com/onsi/ginkgo/v2's changelog.

    2.5.0

    Ginkgo output now includes a timeline-view of the spec

    This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

    The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node > Enter and < Exit events in the spec timeline.

    In addition, JUnit reports now include the timeline (rendered with -vv) and custom JUnit reports can be configured and generated using GenerateJUnitReportWithConfig(report types.Report, dst string, config JunitReportConfig)

    Code should continue to work unchanged with this version of Ginkgo - however if you have tooling that was relying on the specific output format of Ginkgo you may run into issues. Ginkgo's console output is not guaranteed to be stable for tooling and automation purposes. You should, instead, use Ginkgo's JSON format to build tooling on top of as it has stronger guarantees to be stable from version to version.

    Features

    • Provide details about which timeout expired [0f2fa27]

    Fixes

    • Add Support Policy to docs [c70867a]

    Maintenance

    • Bump github.com/onsi/gomega from 1.22.1 to 1.23.0 (#1070) [bb3b4e2]

    2.4.0

    Features

    • DeferCleanup supports functions with multiple-return values [5e33c75]
    • Add GinkgoLogr (#1067) [bf78c28]
    • Introduction of 'MustPassRepeatedly' decorator (#1051) [047c02f]

    Fixes

    • correcting some typos (#1064) [1403d3c]
    • fix flaky internal_integration interupt specs [2105ba3]
    • Correct busted link in README [be6b5b9]

    Maintenance

    • Bump actions/checkout from 2 to 3 (#1062) [8a2f483]
    • Bump golang.org/x/tools from 0.1.12 to 0.2.0 (#1065) [529c4e8]
    • Bump github/codeql-action from 1 to 2 (#1061) [da09146]
    • Bump actions/setup-go from 2 to 3 (#1060) [918040d]

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/gomega from 1.21.1 to 1.24.0

    Bump github.com/onsi/gomega from 1.21.1 to 1.24.0

    Bumps github.com/onsi/gomega from 1.21.1 to 1.24.0.

    Release notes

    Sourced from github.com/onsi/gomega's releases.

    v1.24.0

    1.24.0

    Features

    Introducting gcustom - a convenient mechanism for building custom matchers.

    This is an RC release for gcustom. The external API may be tweaked in response to feedback however it is expected to remain mostly stable.

    Maintenance

    • Update BeComparableTo documentation [756eaa0]

    v1.23.0

    1.23.0

    Features

    • Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

    • Substantial improvement have been made to StopTrying():

      • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
      • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
      • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.
    • TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

    • ctx can now be passed-in as the first argument to Eventually and Consistently.

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.3.0 to 2.3.1 (#597) [afed901]
    • Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#599) [7c691b3]
    • Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#587) [ff22665]

    v1.22.1

    1.22.1

    Fixes

    • When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
    • Allow StopTrying() to be wrapped [bf3cba9]

    Maintenance

    • bump to ginkgo v2.3.0 [c5d5c39]

    v1.22.0

    1.22.0

    Features

    Several improvements have been made to Eventually and Consistently in this and the most recent releases:

    ... (truncated)

    Changelog

    Sourced from github.com/onsi/gomega's changelog.

    1.24.0

    Features

    Introducting gcustom - a convenient mechanism for building custom matchers.

    This is an RC release for gcustom. The external API may be tweaked in response to feedback however it is expected to remain mostly stable.

    Maintenance

    • Update BeComparableTo documentation [756eaa0]

    1.23.0

    Features

    • Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

    • Substantial improvement have been made to StopTrying():

      • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
      • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
      • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.
    • TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

    • ctx can now be passed-in as the first argument to Eventually and Consistently.

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.3.0 to 2.3.1 (#597) [afed901]
    • Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#599) [7c691b3]
    • Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#587) [ff22665]

    1.22.1

    Fixes

    • When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
    • Allow StopTrying() to be wrapped [bf3cba9]

    Maintenance

    • bump to ginkgo v2.3.0 [c5d5c39]

    1.22.0

    Features

    Several improvements have been made to Eventually and Consistently in this and the most recent releases:

    • Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
    • Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]

    ... (truncated)

    Commits
    • ed1156b v1.24.0
    • 756eaa0 Update BeComparableTo documentation
    • 6015576 finish documenting gcustom
    • 0cfc53b godoc for gcustom
    • 6a2e51e First pass at gcustom: a convenience package for making custom matchers. Doc...
    • bf817a4 v1.23.0
    • 7b8b801 fix broken call to Eventually
    • ba35cc6 Allow ctx to be passed in as a leading parameter for Eventually and Consistently
    • 818b78c AsyncAssertions emit the format.Object representation of the error when it i...
    • d63d67e Rename AsyncSignalError to PollingSignalError
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/gomega from 1.21.1 to 1.23.0

    Bump github.com/onsi/gomega from 1.21.1 to 1.23.0

    Bumps github.com/onsi/gomega from 1.21.1 to 1.23.0.

    Release notes

    Sourced from github.com/onsi/gomega's releases.

    v1.23.0

    1.23.0

    Features

    • Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

    • Substantial improvement have been made to StopTrying():

      • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
      • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
      • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.
    • TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

    • ctx can now be passed-in as the first argument to Eventually and Consistently.

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.3.0 to 2.3.1 (#597) [afed901]
    • Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#599) [7c691b3]
    • Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#587) [ff22665]

    v1.22.1

    1.22.1

    Fixes

    • When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
    • Allow StopTrying() to be wrapped [bf3cba9]

    Maintenance

    • bump to ginkgo v2.3.0 [c5d5c39]

    v1.22.0

    1.22.0

    Features

    Several improvements have been made to Eventually and Consistently in this and the most recent releases:

    • Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
    • Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]
    • Eventually/Consistently will forward an attached context to functions that ask for one [e2091c5]
    • Eventually/Consistently supports passing arguments to functions via WithArguments() [a2dc7c3]
    • Eventually and Consistently can now be stopped early with StopTrying(message) and StopTrying(message).Now() [52976bb]

    These improvements are all documented in Gomega's docs

    Changelog

    Sourced from github.com/onsi/gomega's changelog.

    1.23.0

    Features

    • Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

    • Substantial improvement have been made to StopTrying():

      • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
      • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
      • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.
    • TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

    • ctx can now be passed-in as the first argument to Eventually and Consistently.

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.3.0 to 2.3.1 (#597) [afed901]
    • Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#599) [7c691b3]
    • Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#587) [ff22665]

    1.22.1

    Fixes

    • When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
    • Allow StopTrying() to be wrapped [bf3cba9]

    Maintenance

    • bump to ginkgo v2.3.0 [c5d5c39]

    1.22.0

    Features

    Several improvements have been made to Eventually and Consistently in this and the most recent releases:

    • Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
    • Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]
    • Eventually/Consistently will forward an attached context to functions that ask for one [e2091c5]
    • Eventually/Consistently supports passing arguments to functions via WithArguments() [a2dc7c3]
    • Eventually and Consistently can now be stopped early with StopTrying(message) and StopTrying(message).Now() [52976bb]

    These improvements are all documented in Gomega's docs

    Fixes

    Maintenance

    Commits
    • bf817a4 v1.23.0
    • 7b8b801 fix broken call to Eventually
    • ba35cc6 Allow ctx to be passed in as a leading parameter for Eventually and Consistently
    • 818b78c AsyncAssertions emit the format.Object representation of the error when it i...
    • d63d67e Rename AsyncSignalError to PollingSignalError
    • abd25f0 fix go vet
    • 618a133 Introduce TryAgainAfter
    • 67ab22c Simplify StopTrying handling
    • 75c8c70 Fix go vet and drop 1.17 from test matrix
    • 237e97d Matchers can now return StopTrying() errors; StopTrying() can wrap an error t...
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.4.0

    Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.4.0

    Bumps github.com/onsi/ginkgo/v2 from 2.2.0 to 2.4.0.

    Release notes

    Sourced from github.com/onsi/ginkgo/v2's releases.

    v2.4.0

    2.4.0

    Features

    • DeferCleanup supports functions with multiple-return values [5e33c75]
    • Add GinkgoLogr (#1067) [bf78c28]
    • Introduction of 'MustPassRepeatedly' decorator (#1051) [047c02f]

    Fixes

    • correcting some typos (#1064) [1403d3c]
    • fix flaky internal_integration interupt specs [2105ba3]
    • Correct busted link in README [be6b5b9]

    Maintenance

    • Bump actions/checkout from 2 to 3 (#1062) [8a2f483]
    • Bump golang.org/x/tools from 0.1.12 to 0.2.0 (#1065) [529c4e8]
    • Bump github/codeql-action from 1 to 2 (#1061) [da09146]
    • Bump actions/setup-go from 2 to 3 (#1060) [918040d]
    • Bump github.com/onsi/gomega from 1.22.0 to 1.22.1 (#1053) [2098e4d]
    • Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#1066) [1d74122]
    • Add GHA to dependabot config [4442772]

    v2.3.1

    2.3.1

    Fixes

    Several users were invoking ginkgo by installing the latest version of the cli via go install github.com/onsi/ginkgo/v2/ginkgo@latest. When 2.3.0 was released this resulted in an influx of issues as CI systems failed due to a change in the internal contract between the Ginkgo CLI and the Ginkgo library. Ginkgo only supports running the same version of the library as the cli (which is why both are packaged in the same repository).

    With this patch release, the ginkgo CLI can now identify a version mismatch and emit a helpful error message.

    • Ginkgo cli can identify version mismatches and emit a helpful error message [bc4ae2f]
    • further emphasize that a version match is required when running Ginkgo on CI and/or locally [2691dd8]

    Maintenance

    • bump gomega to v1.22.0 [822a937]

    v2.3.0

    2.3.0

    Interruptible Nodes and Timeouts

    Ginkgo now supports per-node and per-spec timeouts on interruptible nodes. Check out the documentation for all the details but the gist is you can now write specs like this:

    It("is interruptible", func(ctx SpecContext) { // or context.Context instead of SpecContext, both are valid.
        // do things until `ctx.Done()` is closed, for example:
        req, err := http.NewRequestWithContext(ctx, "POST", "/build-widgets", nil)
        Expect(err).NotTo(HaveOccured())
        _, err := http.DefaultClient.Do(req)
    </tr></table> 
    

    ... (truncated)

    Changelog

    Sourced from github.com/onsi/ginkgo/v2's changelog.

    2.4.0

    Features

    • DeferCleanup supports functions with multiple-return values [5e33c75]
    • Add GinkgoLogr (#1067) [bf78c28]
    • Introduction of 'MustPassRepeatedly' decorator (#1051) [047c02f]

    Fixes

    • correcting some typos (#1064) [1403d3c]
    • fix flaky internal_integration interupt specs [2105ba3]
    • Correct busted link in README [be6b5b9]

    Maintenance

    • Bump actions/checkout from 2 to 3 (#1062) [8a2f483]
    • Bump golang.org/x/tools from 0.1.12 to 0.2.0 (#1065) [529c4e8]
    • Bump github/codeql-action from 1 to 2 (#1061) [da09146]
    • Bump actions/setup-go from 2 to 3 (#1060) [918040d]
    • Bump github.com/onsi/gomega from 1.22.0 to 1.22.1 (#1053) [2098e4d]
    • Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#1066) [1d74122]
    • Add GHA to dependabot config [4442772]

    2.3.1

    Fixes

    Several users were invoking ginkgo by installing the latest version of the cli via go install github.com/onsi/ginkgo/v2/ginkgo@latest. When 2.3.0 was released this resulted in an influx of issues as CI systems failed due to a change in the internal contract between the Ginkgo CLI and the Ginkgo library. Ginkgo only supports running the same version of the library as the cli (which is why both are packaged in the same repository).

    With this patch release, the ginkgo CLI can now identify a version mismatch and emit a helpful error message.

    • Ginkgo cli can identify version mismatches and emit a helpful error message [bc4ae2f]
    • further emphasize that a version match is required when running Ginkgo on CI and/or locally [2691dd8]

    Maintenance

    • bump gomega to v1.22.0 [822a937]

    2.3.0

    Interruptible Nodes and Timeouts

    Ginkgo now supports per-node and per-spec timeouts on interruptible nodes. Check out the documentation for all the details but the gist is you can now write specs like this:

    It("is interruptible", func(ctx SpecContext) { // or context.Context instead of SpecContext, both are valid.
        // do things until `ctx.Done()` is closed, for example:
        req, err := http.NewRequestWithContext(ctx, "POST", "/build-widgets", nil)
        Expect(err).NotTo(HaveOccured())
        _, err := http.DefaultClient.Do(req)
        Expect(err).NotTo(HaveOccured())
    
    Eventually(client.WidgetCount).WithContext(ctx).Should(Equal(17))
    

    </tr></table>

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.3.1

    Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.3.1

    Bumps github.com/onsi/ginkgo/v2 from 2.2.0 to 2.3.1.

    Release notes

    Sourced from github.com/onsi/ginkgo/v2's releases.

    v2.3.1

    2.3.1

    Fixes

    Several users were invoking ginkgo by installing the latest version of the cli via go install github.com/onsi/ginkgo/v2/ginkgo@latest. When 2.3.0 was released this resulted in an influx of issues as CI systems failed due to a change in the internal contract between the Ginkgo CLI and the Ginkgo library. Ginkgo only supports running the same version of the library as the cli (which is why both are packaged in the same repository).

    With this patch release, the ginkgo CLI can now identify a version mismatch and emit a helpful error message.

    • Ginkgo cli can identify version mismatches and emit a helpful error message [bc4ae2f]
    • further emphasize that a version match is required when running Ginkgo on CI and/or locally [2691dd8]

    Maintenance

    • bump gomega to v1.22.0 [822a937]

    v2.3.0

    2.3.0

    Interruptible Nodes and Timeouts

    Ginkgo now supports per-node and per-spec timeouts on interruptible nodes. Check out the documentation for all the details but the gist is you can now write specs like this:

    It("is interruptible", func(ctx SpecContext) { // or context.Context instead of SpecContext, both are valid.
        // do things until `ctx.Done()` is closed, for example:
        req, err := http.NewRequestWithContext(ctx, "POST", "/build-widgets", nil)
        Expect(err).NotTo(HaveOccured())
        _, err := http.DefaultClient.Do(req)
        Expect(err).NotTo(HaveOccured())
    
    Eventually(client.WidgetCount).WithContext(ctx).Should(Equal(17))
    

    }, NodeTimeout(time.Second20), GracePeriod(5time.Second))

    and have Ginkgo ensure that the node completes before the timeout elapses. If it does elapse, or if an external interrupt is received (e.g. ^C) then Ginkgo will cancel the context and wait for the Grace Period for the node to exit before proceeding with any cleanup nodes associated with the spec. The ctx provided by Ginkgo can also be passed down to Gomega's Eventually to have all assertions within the node governed by a single deadline.

    Features

    • Ginkgo now records any additional failures that occur during the cleanup of a failed spec. In prior versions this information was quietly discarded, but the introduction of a more rigorous approach to timeouts and interruptions allows Ginkgo to better track subsequent failures.
    • SpecContext also provides a mechanism for third-party libraries to provide additional information when a Progress Report is generated. Gomega uses this to provide the current state of an Eventually().WithContext() assertion when a Progress Report is requested.
    • DescribeTable now exits with an error if it is not passed any Entries [a4c9865]

    Fixes

    • fixes crashes on newer Ruby 3 installations by upgrading github-pages gem dependency [92c88d5]
    • Make the outline command able to use the DSL import [1be2427]

    Maintenance

    • chore(docs): delete no meaning d [57c373c]
    • chore(docs): Fix hyperlinks [30526d5]
    • chore(docs): fix code blocks without language settings [cf611c4]
    • fix intra-doc link [b541bcb]
    Changelog

    Sourced from github.com/onsi/ginkgo/v2's changelog.

    2.3.1

    Fixes

    Several users were invoking ginkgo by installing the latest version of the cli via go install github.com/onsi/ginkgo/v2/ginkgo@latest. When 2.3.0 was released this resulted in an influx of issues as CI systems failed due to a change in the internal contract between the Ginkgo CLI and the Ginkgo library. Ginkgo only supports running the same version of the library as the cli (which is why both are packaged in the same repository).

    With this patch release, the ginkgo CLI can now identify a version mismatch and emit a helpful error message.

    • Ginkgo cli can identify version mismatches and emit a helpful error message [bc4ae2f]
    • further emphasize that a version match is required when running Ginkgo on CI and/or locally [2691dd8]

    Maintenance

    • bump gomega to v1.22.0 [822a937]

    2.3.0

    Interruptible Nodes and Timeouts

    Ginkgo now supports per-node and per-spec timeouts on interruptible nodes. Check out the documentation for all the details but the gist is you can now write specs like this:

    It("is interruptible", func(ctx SpecContext) { // or context.Context instead of SpecContext, both are valid.
        // do things until `ctx.Done()` is closed, for example:
        req, err := http.NewRequestWithContext(ctx, "POST", "/build-widgets", nil)
        Expect(err).NotTo(HaveOccured())
        _, err := http.DefaultClient.Do(req)
        Expect(err).NotTo(HaveOccured())
    
    Eventually(client.WidgetCount).WithContext(ctx).Should(Equal(17))
    

    }, NodeTimeout(time.Second20), GracePeriod(5time.Second))

    and have Ginkgo ensure that the node completes before the timeout elapses. If it does elapse, or if an external interrupt is received (e.g. ^C) then Ginkgo will cancel the context and wait for the Grace Period for the node to exit before proceeding with any cleanup nodes associated with the spec. The ctx provided by Ginkgo can also be passed down to Gomega's Eventually to have all assertions within the node governed by a single deadline.

    Features

    • Ginkgo now records any additional failures that occur during the cleanup of a failed spec. In prior versions this information was quietly discarded, but the introduction of a more rigorous approach to timeouts and interruptions allows Ginkgo to better track subsequent failures.
    • SpecContext also provides a mechanism for third-party libraries to provide additional information when a Progress Report is generated. Gomega uses this to provide the current state of an Eventually().WithContext() assertion when a Progress Report is requested.
    • DescribeTable now exits with an error if it is not passed any Entries [a4c9865]

    Fixes

    • fixes crashes on newer Ruby 3 installations by upgrading github-pages gem dependency [92c88d5]
    • Make the outline command able to use the DSL import [1be2427]

    Maintenance

    • chore(docs): delete no meaning d [57c373c]
    • chore(docs): Fix hyperlinks [30526d5]
    • chore(docs): fix code blocks without language settings [cf611c4]
    • fix intra-doc link [b541bcb]
    Commits
    • 2cc2219 v2.3.1
    • bc4ae2f Ginkgo cli can identify version mismatches and emit a helpful error message
    • 2691dd8 further emphasize that a version match is required when running Ginkgo on CI ...
    • 822a937 bump gomega to v1.22.0
    • 87fc2ec v2.3.0
    • bda6ffe clarify what we mean by cleanup nodes
    • b182b1f document how SpecContext and Eventually work together
    • 5ddc567 be more consistent about 'Timedout' vs 'Timeout'
    • a87ec82 Gingko now records additional failures that occur during cleanup of a failed ...
    • cd395fc ensure post-timeout failure makes it into the JUnit report
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/gomega from 1.21.1 to 1.22.1

    Bump github.com/onsi/gomega from 1.21.1 to 1.22.1

    Bumps github.com/onsi/gomega from 1.21.1 to 1.22.1.

    Release notes

    Sourced from github.com/onsi/gomega's releases.

    v1.22.1

    1.22.1

    Fixes

    • When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
    • Allow StopTrying() to be wrapped [bf3cba9]

    Maintenance

    • bump to ginkgo v2.3.0 [c5d5c39]

    v1.22.0

    1.22.0

    Features

    Several improvements have been made to Eventually and Consistently in this and the most recent releases:

    • Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
    • Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]
    • Eventually/Consistently will forward an attached context to functions that ask for one [e2091c5]
    • Eventually/Consistently supports passing arguments to functions via WithArguments() [a2dc7c3]
    • Eventually and Consistently can now be stopped early with StopTrying(message) and StopTrying(message).Now() [52976bb]

    These improvements are all documented in Gomega's docs

    Changelog

    Sourced from github.com/onsi/gomega's changelog.

    1.22.1

    Fixes

    • When passed a context and no explicit timeout, Eventually will only timeout when the context is cancelled [e5105cf]
    • Allow StopTrying() to be wrapped [bf3cba9]

    Maintenance

    • bump to ginkgo v2.3.0 [c5d5c39]

    1.22.0

    Features

    Several improvements have been made to Eventually and Consistently in this and the most recent releases:

    • Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
    • Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]
    • Eventually/Consistently will forward an attached context to functions that ask for one [e2091c5]
    • Eventually/Consistently supports passing arguments to functions via WithArguments() [a2dc7c3]
    • Eventually and Consistently can now be stopped early with StopTrying(message) and StopTrying(message).Now() [52976bb]

    These improvements are all documented in Gomega's docs

    Fixes

    Maintenance

    Commits
    • 40d0cc9 v1.22.1
    • e5105cf When passed a context and no explicit timeout, Eventually will only timeout w...
    • bf3cba9 Allow StopTrying() to be wrapped
    • c5d5c39 bump to ginkgo v2.3.0
    • 8916066 v1.22.0
    • aeab53a fix go vet issue
    • 52976bb Eventually an Consistently can now be stopped early with StopTrying(message) ...
    • a2dc7c3 Gomega supports passing arguments to functions via WithArguments()
    • e2091c5 Eventually/Consistently will forward an attached context to functions that as...
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/gomega from 1.20.0 to 1.20.2

    Bump github.com/onsi/gomega from 1.20.0 to 1.20.2

    Bumps github.com/onsi/gomega from 1.20.0 to 1.20.2.

    Release notes

    Sourced from github.com/onsi/gomega's releases.

    v1.20.2

    1.20.2

    Fixes

    • label specs that rely on remote access; bump timeout on short-circuit test to make it less flaky [35eeadf]
    • gexec: allow more headroom for SIGABRT-related unit tests (#581) [5b78f40]
    • Enable reading from a closed gbytes.Buffer (#575) [061fd26]

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.1.5 to 2.1.6 (#583) [55d895b]
    • Bump github.com/onsi/ginkgo/v2 from 2.1.4 to 2.1.5 (#582) [346de7c]

    v1.20.1

    1.20.1

    Fixes

    • fix false positive gleaks when using ginkgo -p (#577) [cb46517]
    • Fix typos in gomega_dsl.go (#569) [5f71ed2]
    • don't panic on Eventually(nil), fixing #555 (#567) [9d1186f]
    • vet optional description args in assertions, fixing #560 (#566) [8e37808]

    Maintenance

    • test: add new Go 1.19 to test matrix (#571) [40d7efe]
    • Bump tzinfo from 1.2.9 to 1.2.10 in /docs (#564) [5f26371]
    Changelog

    Sourced from github.com/onsi/gomega's changelog.

    1.20.2

    Fixes

    • label specs that rely on remote access; bump timeout on short-circuit test to make it less flaky [35eeadf]
    • gexec: allow more headroom for SIGABRT-related unit tests (#581) [5b78f40]
    • Enable reading from a closed gbytes.Buffer (#575) [061fd26]

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.1.5 to 2.1.6 (#583) [55d895b]
    • Bump github.com/onsi/ginkgo/v2 from 2.1.4 to 2.1.5 (#582) [346de7c]

    1.20.1

    Fixes

    • fix false positive gleaks when using ginkgo -p (#577) [cb46517]
    • Fix typos in gomega_dsl.go (#569) [5f71ed2]
    • don't panic on Eventually(nil), fixing #555 (#567) [9d1186f]
    • vet optional description args in assertions, fixing #560 (#566) [8e37808]

    Maintenance

    • test: add new Go 1.19 to test matrix (#571) [40d7efe]
    • Bump tzinfo from 1.2.9 to 1.2.10 in /docs (#564) [5f26371]
    Commits
    • 604aef4 v1.20.2
    • 35eeadf label specs that rely on remote access; bump timeout on short-circuit test to...
    • 55d895b Bump github.com/onsi/ginkgo/v2 from 2.1.5 to 2.1.6 (#583)
    • 346de7c Bump github.com/onsi/ginkgo/v2 from 2.1.4 to 2.1.5 (#582)
    • 5b78f40 gexec: allow more headroom for SIGABRT-related unit tests (#581)
    • 061fd26 Enable reading from a closed gbytes.Buffer (#575)
    • 758e947 v1.20.1
    • cb46517 fix false positive gleaks when using ginkgo -p (#577)
    • 40d7efe test: add new Go 1.19 to test matrix (#571)
    • 5f71ed2 Fix typos in gomega_dsl.go (#569)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/gomega from 1.20.0 to 1.21.1

    Bump github.com/onsi/gomega from 1.20.0 to 1.21.1

    Bumps github.com/onsi/gomega from 1.20.0 to 1.21.1.

    Release notes

    Sourced from github.com/onsi/gomega's releases.

    v1.21.1

    Features

    • Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]

    v1.21.0

    1.21.0

    Features

    • Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
    • Introduces Eventually.Within.ProbeEvery with tests and documentation (#591) [f633800]
    • New BeKeyOf matcher with documentation and unit tests (#590) [fb586b3]

    Fixes

    • Cover the entire gmeasure suite with leak detection [8c54344]
    • Fix gmeasure leak [119d4ce]
    • Ignore new Ginkgo ProgressSignal goroutine in gleak [ba548e2]

    Maintenance

    • Fixes crashes on newer Ruby 3 installations by upgrading github-pages gem dependency (#596) [12469a0]

    v1.20.2

    1.20.2

    Fixes

    • label specs that rely on remote access; bump timeout on short-circuit test to make it less flaky [35eeadf]
    • gexec: allow more headroom for SIGABRT-related unit tests (#581) [5b78f40]
    • Enable reading from a closed gbytes.Buffer (#575) [061fd26]

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.1.5 to 2.1.6 (#583) [55d895b]
    • Bump github.com/onsi/ginkgo/v2 from 2.1.4 to 2.1.5 (#582) [346de7c]

    v1.20.1

    1.20.1

    Fixes

    • fix false positive gleaks when using ginkgo -p (#577) [cb46517]
    • Fix typos in gomega_dsl.go (#569) [5f71ed2]
    • don't panic on Eventually(nil), fixing #555 (#567) [9d1186f]
    • vet optional description args in assertions, fixing #560 (#566) [8e37808]

    Maintenance

    • test: add new Go 1.19 to test matrix (#571) [40d7efe]
    • Bump tzinfo from 1.2.9 to 1.2.10 in /docs (#564) [5f26371]
    Changelog

    Sourced from github.com/onsi/gomega's changelog.

    v1.21.1

    Features

    • Eventually and Consistently that are passed a SpecContext can provide reports when an interrupt occurs [0d063c9]

    1.21.0

    Features

    • Eventually and Consistently can take a context.Context [65c01bc] This enables integration with Ginkgo 2.3.0's interruptible nodes and node timeouts.
    • Introduces Eventually.Within.ProbeEvery with tests and documentation (#591) [f633800]
    • New BeKeyOf matcher with documentation and unit tests (#590) [fb586b3]

    Fixes

    • Cover the entire gmeasure suite with leak detection [8c54344]
    • Fix gmeasure leak [119d4ce]
    • Ignore new Ginkgo ProgressSignal goroutine in gleak [ba548e2]

    Maintenance

    • Fixes crashes on newer Ruby 3 installations by upgrading github-pages gem dependency (#596) [12469a0]

    1.20.2

    Fixes

    • label specs that rely on remote access; bump timeout on short-circuit test to make it less flaky [35eeadf]
    • gexec: allow more headroom for SIGABRT-related unit tests (#581) [5b78f40]
    • Enable reading from a closed gbytes.Buffer (#575) [061fd26]

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.1.5 to 2.1.6 (#583) [55d895b]
    • Bump github.com/onsi/ginkgo/v2 from 2.1.4 to 2.1.5 (#582) [346de7c]

    1.20.1

    Fixes

    • fix false positive gleaks when using ginkgo -p (#577) [cb46517]
    • Fix typos in gomega_dsl.go (#569) [5f71ed2]
    • don't panic on Eventually(nil), fixing #555 (#567) [9d1186f]
    • vet optional description args in assertions, fixing #560 (#566) [8e37808]

    Maintenance

    • test: add new Go 1.19 to test matrix (#571) [40d7efe]
    • Bump tzinfo from 1.2.9 to 1.2.10 in /docs (#564) [5f26371]
    Commits
    • 2e34979 v1.21.1
    • 0d063c9 Eventually and Consistently that are passed a SpecContext can provide reports...
    • 2ba5763 v1.21.0
    • 65c01bc Eventually and Consistently can take a context.Context
    • 12469a0 fixes crashes on newer Ruby 3 installations by upgrading github-pages gem dep...
    • b8636ad documentation updates for BeKeyOf and well-known non-leaky goroutines (#592)
    • f633800 introduces Eventually.Within.ProbeEvery with tests and documentation (#591)
    • fb586b3 new BeKeyOf matcher with documentation and unit tests (#590)
    • 647a36b welp; remove local Ginkgo replace directive in go.mod
    • 8c54344 cover the entire gmeasure suite with leak detection
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/gomega from 1.21.1 to 1.24.2

    Bump github.com/onsi/gomega from 1.21.1 to 1.24.2

    Bumps github.com/onsi/gomega from 1.21.1 to 1.24.2.

    Release notes

    Sourced from github.com/onsi/gomega's releases.

    v1.24.2

    1.24.2

    Fixes

    • Correctly handle assertion failure panics for eventually/consistnetly "g Gomega"s in a goroutine [78f1660]
    • docs:Fix typo "you an" -> "you can" (#607) [3187c1f]
    • fixes issue #600 (#606) [808d192]

    Maintenance

    • Bump golang.org/x/net from 0.2.0 to 0.4.0 (#611) [6ebc0bf]
    • Bump nokogiri from 1.13.9 to 1.13.10 in /docs (#612) [258cfc8]
    • Bump github.com/onsi/ginkgo/v2 from 2.5.0 to 2.5.1 (#609) [e6c3eb9]

    v1.24.1

    No release notes provided.

    v1.24.0

    1.24.0

    Features

    Introducting gcustom - a convenient mechanism for building custom matchers.

    This is an RC release for gcustom. The external API may be tweaked in response to feedback however it is expected to remain mostly stable.

    Maintenance

    • Update BeComparableTo documentation [756eaa0]

    v1.23.0

    1.23.0

    Features

    • Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

    • Substantial improvement have been made to StopTrying():

      • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
      • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
      • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.
    • TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

    • ctx can now be passed-in as the first argument to Eventually and Consistently.

    Maintenance

    • Bump github.com/onsi/ginkgo/v2 from 2.3.0 to 2.3.1 (#597) [afed901]
    • Bump nokogiri from 1.13.8 to 1.13.9 in /docs (#599) [7c691b3]
    • Bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#587) [ff22665]

    ... (truncated)

    Changelog

    Sourced from github.com/onsi/gomega's changelog.

    1.24.2

    Fixes

    • Correctly handle assertion failure panics for eventually/consistnetly "g Gomega"s in a goroutine [78f1660]
    • docs:Fix typo "you an" -> "you can" (#607) [3187c1f]
    • fixes issue #600 (#606) [808d192]

    Maintenance

    • Bump golang.org/x/net from 0.2.0 to 0.4.0 (#611) [6ebc0bf]
    • Bump nokogiri from 1.13.9 to 1.13.10 in /docs (#612) [258cfc8]
    • Bump github.com/onsi/ginkgo/v2 from 2.5.0 to 2.5.1 (#609) [e6c3eb9]

    1.24.1

    Fixes

    • maintain backward compatibility for Eventually and Consisntetly's signatures [4c7df5e]
    • fix small typo (#601) [ea0ebe6]

    Maintenance

    • Bump golang.org/x/net from 0.1.0 to 0.2.0 (#603) [1ba8372]
    • Bump github.com/onsi/ginkgo/v2 from 2.4.0 to 2.5.0 (#602) [f9426cb]
    • fix label-filter in test.yml [d795db6]
    • stop running flakey tests and rely on external network dependencies in CI [7133290]

    1.24.0

    Features

    Introducting gcustom - a convenient mechanism for building custom matchers.

    This is an RC release for gcustom. The external API may be tweaked in response to feedback however it is expected to remain mostly stable.

    Maintenance

    • Update BeComparableTo documentation [756eaa0]

    1.23.0

    Features

    • Custom formatting on a per-type basis can be provided using format.RegisterCustomFormatter() -- see the docs here

    • Substantial improvement have been made to StopTrying():

      • Users can now use StopTrying().Wrap(err) to wrap errors and StopTrying().Attach(description, object) to attach arbitrary objects to the StopTrying() error
      • StopTrying() is now always interpreted as a failure. If you are an early adopter of StopTrying() you may need to change your code as the prior version would match against the returned value even if StopTrying() was returned. Going forward the StopTrying() api should remain stable.
      • StopTrying() and StopTrying().Now() can both be used in matchers - not just polled functions.
    • TryAgainAfter(duration) is used like StopTrying() but instructs Eventually and Consistently that the poll should be tried again after the specified duration. This allows you to dynamically adjust the polling duration.

    • ctx can now be passed-in as the first argument to Eventually and Consistently.

    ... (truncated)

    Commits
    • c3aef8b v1.24.2
    • 78f1660 Correctly handle assertion failure panics for eventually/consistnetly "g Gom...
    • 6ebc0bf Bump golang.org/x/net from 0.2.0 to 0.4.0 (#611)
    • 258cfc8 Bump nokogiri from 1.13.9 to 1.13.10 in /docs (#612)
    • e6c3eb9 Bump github.com/onsi/ginkgo/v2 from 2.5.0 to 2.5.1 (#609)
    • 3187c1f docs:Fix typo "you an" -> "you can" (#607)
    • 808d192 fixes issue #600 (#606)
    • 3eef0d7 v1.24.1
    • 4c7df5e maintain backward compatibility for Eventually and Consisntetly's signatures
    • 1ba8372 Bump golang.org/x/net from 0.1.0 to 0.2.0 (#603)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.6.1

    Bump github.com/onsi/ginkgo/v2 from 2.2.0 to 2.6.1

    Bumps github.com/onsi/ginkgo/v2 from 2.2.0 to 2.6.1.

    Release notes

    Sourced from github.com/onsi/ginkgo/v2's releases.

    v2.6.1

    2.6.1

    Features

    • Override formatter colors from envvars - this is a new feature but an alternative approach involving config files might be taken in the future (#1095) [60240d1]

    Fixes

    • GinkgoRecover now supports ignoring panics that match a specific, hidden, interface [301f3e2]

    Maintenance

    • Bump github.com/onsi/gomega from 1.24.0 to 1.24.1 (#1077) [3643823]
    • Bump golang.org/x/tools from 0.2.0 to 0.4.0 (#1090) [f9f856e]
    • Bump nokogiri from 1.13.9 to 1.13.10 in /docs (#1091) [0d7087e]

    v2.6.0

    2.6.0

    Features

    • ReportBeforeSuite provides access to the suite report before the suite begins.
    • Add junit config option for omitting leafnodetype (#1088) [956e6d2]
    • Add support to customize junit report config to omit spec labels (#1087) [de44005]

    Fixes

    • Fix stack trace pruning so that it has a chance of working on windows [2165648]

    v2.5.1

    2.5.1

    Fixes

    • skipped tests only show as 'S' when running with -v [3ab38ae]
    • Fix typo in docs/index.md (#1082) [55fc58d]
    • Fix typo in docs/index.md (#1081) [8a14f1f]
    • Fix link notation in docs/index.md (#1080) [2669612]
    • Fix typo in --progress deprecation message (#1076) [b4b7edc]

    Maintenance

    • chore: Included githubactions in the dependabot config (#976) [baea341]
    • Bump golang.org/x/sys from 0.1.0 to 0.2.0 (#1075) [9646297]

    v2.5.0

    2.5.0

    Ginkgo output now includes a timeline-view of the spec

    This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

    The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags

    ... (truncated)

    Changelog

    Sourced from github.com/onsi/ginkgo/v2's changelog.

    2.6.1

    Features

    • Override formatter colors from envvars - this is a new feature but an alternative approach involving config files might be taken in the future (#1095) [60240d1]

    Fixes

    • GinkgoRecover now supports ignoring panics that match a specific, hidden, interface [301f3e2]

    Maintenance

    • Bump github.com/onsi/gomega from 1.24.0 to 1.24.1 (#1077) [3643823]
    • Bump golang.org/x/tools from 0.2.0 to 0.4.0 (#1090) [f9f856e]
    • Bump nokogiri from 1.13.9 to 1.13.10 in /docs (#1091) [0d7087e]

    2.6.0

    Features

    • ReportBeforeSuite provides access to the suite report before the suite begins.
    • Add junit config option for omitting leafnodetype (#1088) [956e6d2]
    • Add support to customize junit report config to omit spec labels (#1087) [de44005]

    Fixes

    • Fix stack trace pruning so that it has a chance of working on windows [2165648]

    2.5.1

    Fixes

    • skipped tests only show as 'S' when running with -v [3ab38ae]
    • Fix typo in docs/index.md (#1082) [55fc58d]
    • Fix typo in docs/index.md (#1081) [8a14f1f]
    • Fix link notation in docs/index.md (#1080) [2669612]
    • Fix typo in --progress deprecation message (#1076) [b4b7edc]

    Maintenance

    • chore: Included githubactions in the dependabot config (#976) [baea341]
    • Bump golang.org/x/sys from 0.1.0 to 0.2.0 (#1075) [9646297]

    2.5.0

    Ginkgo output now includes a timeline-view of the spec

    This commit changes Ginkgo's default output. Spec details are now presented as a timeline that includes events that occur during the spec lifecycle interleaved with any GinkgoWriter content. This makes is much easier to understand the flow of a spec and where a given failure occurs.

    The --progress, --slow-spec-threshold, --always-emit-ginkgo-writer flags and the SuppressProgressReporting decorator have all been deprecated. Instead the existing -v and -vv flags better capture the level of verbosity to display. However, a new --show-node-events flag is added to include node > Enter and < Exit events in the spec timeline.

    ... (truncated)

    Commits
    • e7e3db7 v2.6.1
    • 301f3e2 GinkgoRecover now supports ignoring panics that match a specific, hidden, int...
    • 60240d1 Override formatter colors from envvars (#1095)
    • 3643823 Bump github.com/onsi/gomega from 1.24.0 to 1.24.1 (#1077)
    • f9f856e Bump golang.org/x/tools from 0.2.0 to 0.4.0 (#1090)
    • 0d7087e Bump nokogiri from 1.13.9 to 1.13.10 in /docs (#1091)
    • 6ad4fae v2.6.0
    • 366815d fix race in internal integration spec
    • 1869212 Refactor and clean up ReportBeforeSuite additions.
    • 52b4b9c ReportBeforeSuite provides the suite report before the suite begins
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Related tags
A JSON parser/generator for Go

FASTJSON fastjson是java版本的fastjson库的api做一个翻译,方便习惯java的人操作json数据 主要适用场景:层级和字段都不能确定的json 这个库并不实现高性能json解析,依赖标准库json 这个库并没有100%实现java版的api 安装 go get -u gi

Dec 29, 2021
JSON query in Golang

gojq JSON query in Golang. Install go get -u github.com/elgs/gojq This library serves three purposes: makes parsing JSON configuration file much easie

Dec 28, 2022
Automatically generate Go (golang) struct definitions from example JSON

gojson gojson generates go struct definitions from json or yaml documents. Example $ curl -s https://api.github.com/repos/chimeracoder/gojson | gojson

Jan 1, 2023
Arbitrary transformations of JSON in Golang

kazaam Description Kazaam was created with the goal of supporting easy and fast transformations of JSON data with Golang. This functionality provides

Dec 18, 2022
Parsing JSON is a hassle in golang

GoJSON Parsing JSON is a hassle in golang. This package will allow you to parse and search elements in a json without structs. Install gojson go get g

Nov 12, 2021
Fast JSON serializer for golang.

easyjson Package easyjson provides a fast and easy way to marshal/unmarshal Go structs to/from JSON without the use of reflection. In performance test

Jan 4, 2023
Fastest JSON interperter for golang

Welcome To JIN "Your wish is my command" Fast and Easy Way to Deal With JSON Jin is a comprehensive JSON manipulation tool bundle. All functions teste

Dec 14, 2022
Fast Color JSON Marshaller + Pretty Printer for Golang
Fast Color JSON Marshaller + Pretty Printer for Golang

ColorJSON: The Fast Color JSON Marshaller for Go What is this? This package is based heavily on hokaccha/go-prettyjson but has some noticible differen

Dec 19, 2022
Golang port of simdjson: parsing gigabytes of JSON per second
Golang port of simdjson: parsing gigabytes of JSON per second

This is a Golang port of simdjson, a high performance JSON parser developed by Daniel Lemire and Geoff Langdale. It makes extensive use of SIMD instructions to achieve parsing performance of gigabytes of JSON per second.

Dec 30, 2022
Scan Fastjson Use Golang Only

SuperFastjsonScan 该工具仅是Demo版,并不完善,给各位提供一个思路 参考工具:https://github.com/EmYiQing/XiuScan/ 该工具的核心是:不搭建JNDI Server或LDAP Server,也不用Dnslog平台,即可进行无回显Java反序列化漏洞

Dec 16, 2021
Kazaam was created with the goal of supporting easy and fast transformations of JSON data with Golang

kazaam Description Kazaam was created with the goal of supporting easy and fast transformations of JSON data with Golang. This functionality provides

Sep 17, 2021
Copy of Golang's json library with IsZero feature

json Copy of Golang's json library with IsZero feature from CL13977 Disclaimer It is a package primary used for my own projects, I will keep it up-to-

Oct 9, 2021
Golang JSON decoder supporting case-sensitive, number-preserving, and strict decoding use cases

Golang JSON decoder supporting case-sensitive, number-preserving, and strict decoding use cases

Dec 9, 2022
Benchmark of Golang JSON Libraries

Introduction This is a benchmark for the json packages. You are welcome to open an issue if you find anything wrong or out of date. TL;DR In conclusio

Nov 3, 2022
Example to validate performance using append or not in golang

benchtest-arr-go This code is a example to validate performance using append or not in golang result benchtests go test -benchmem -bench . goos: darwi

Jan 10, 2022
Senml-go - a Golang module for the JSON-based SenML sensor data format

ThingWave SenML module for Golang This is a Golang module for the JSON-based Sen

Jan 2, 2022
Decode / encode XML to/from map[string]interface{} (or JSON); extract values with dot-notation paths and wildcards. Replaces x2j and j2x packages.

mxj - to/from maps, XML and JSON Decode/encode XML to/from map[string]interface{} (or JSON) values, and extract/modify values from maps by key or key-

Dec 29, 2022
Abstract JSON for golang with JSONPath support

Abstract JSON Abstract JSON is a small golang package provides a parser for JSON with support of JSONPath, in case when you are not sure in its struct

Jan 5, 2023
a cheat-sheet for mathematical notation in code form

math-as-code Chinese translation (中文版) Python version (English) This is a reference to ease developers into mathematical notation by showing compariso

Dec 27, 2022
Parses the Graphviz DOT language in golang

Parses the Graphviz DOT language and creates an interface, in golang, with which to easily create new and manipulate existing graphs which can be writ

Dec 25, 2022