refactor: remove format #12
Annotations
11 warnings
|
CI Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
CI Build:
tests/DotBahn.Tests.Stations/Client/StationsClientTests.cs#L52
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
CI Build:
tests/DotBahn.Tests.Stations/Client/StationsClientTests.cs#L32
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
CI Build:
tests/DotBahn.Tests.Facilities/Client/FacilitiesClientTests.cs#L74
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
CI Build:
tests/DotBahn.Tests.Facilities/Client/FacilitiesClientTests.cs#L65
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
CI Build:
tests/DotBahn.Tests.Facilities/Client/FacilitiesClientTests.cs#L51
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
CI Build:
tests/DotBahn.Tests.Facilities/Client/FacilitiesClientTests.cs#L35
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
CI Build:
tests/DotBahn.Tests.Stations/Client/StationsClientTests.cs#L85
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
CI Build:
tests/DotBahn.Tests.Stations/Client/StationsClientTests.cs#L73
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
CI Build:
tests/DotBahn.Tests.Stations/Client/StationsClientTests.cs#L52
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
CI Build:
tests/DotBahn.Tests.Stations/Client/StationsClientTests.cs#L32
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|