Bump Testcontainers.MariaDb and Testcontainers #2247
dependabot[bot]Annotations
99 warnings
|
build (integration-tests-sqlcontroller-checklists)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.Integration.Case.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.Integration.CheckLists.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.Integration.Base.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.Integration.Base.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.CheckLists.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-checklists):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (unit-tests-checklists):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists):
eFormSDK.Integration.Base.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists):
eFormSDK.Integration.Base.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists):
eFormSDK.Integration.Case.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists):
eFormSDK.CheckLists.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists):
eFormSDK.Integration.CheckLists.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-checklists):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (unit-tests-insight):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight):
eFormSDK.Integration.Base.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight):
eFormSDK.Integration.Base.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight):
eFormSDK.CheckLists.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight):
eFormSDK.Integration.CheckLists.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight):
eFormSDK.Integration.Case.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-insight):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (integration-tests-core-base):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base):
eFormSDK.Integration.Base.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base):
eFormSDK.Integration.Base.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base):
eFormSDK.Integration.Case.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base):
eFormSDK.CheckLists.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base):
eFormSDK.Integration.CheckLists.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-base):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (integration-tests-core-case):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case):
eFormSDK.Integration.Base.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case):
eFormSDK.Integration.Base.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case):
eFormSDK.CheckLists.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case):
eFormSDK.Integration.CheckLists.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case):
eFormSDK.Integration.Case.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-case):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (unit-tests-base):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base):
eFormSDK.Integration.Base.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base):
eFormSDK.Integration.Case.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base):
eFormSDK.Integration.Base.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base):
eFormSDK.Integration.CheckLists.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base):
eFormSDK.CheckLists.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (unit-tests-base):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.Integration.Base.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.Integration.Base.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.Integration.Case.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.Integration.CheckLists.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.CheckLists.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-base):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.Integration.Base.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.Integration.Base.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.Integration.Case.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.CheckLists.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.Integration.CheckLists.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-sqlcontroller-case):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
build (integration-tests-core-checklists):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists):
eFormSDK.Integration.Base.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists):
eFormSDK.InSight.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists):
eFormSDK.Integration.Case.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists):
eFormSDK.Integration.Base.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists):
eFormSDK.CheckLists.Tests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists):
eFormSDK.Integration.CheckLists.CoreTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists):
eFormSDK.Integration.Case.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists):
eFormSDK.Integration.CheckLists.SqlControllerTests/DbTestFixture.cs#L185
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|
|
build (integration-tests-core-checklists):
eFormSDK.Base.Tests/DbTestFixture.cs#L207
Method 'ExecuteSqlRawAsync' inserts interpolated strings directly into the SQL, without any protection against SQL injection. Consider using 'ExecuteSqlAsync' instead, which protects against SQL injection, or make sure that the value is sanitized and suppress the warning.
|