Files

GitHub Actions 8294d6ee49 Add QA test outputs, build scripts, and Dockerfile validation

- Created `qa-test-output-after-fix.txt` and `qa-test-output.txt` to log results of certificate page authentication tests.
- Added `build.sh` for deterministic backend builds in CI, utilizing `go list` for efficiency.
- Introduced `codeql_scan.sh` for CodeQL database creation and analysis for Go and JavaScript/TypeScript.
- Implemented `dockerfile_check.sh` to validate Dockerfiles for base image and package manager mismatches.
- Added `sourcery_precommit_wrapper.sh` to facilitate Sourcery CLI usage in pre-commit hooks.

2025-12-11 18:26:24 +00:00

1.1 KiB

Raw Blame History

Plan: Fix 'No packages found' for Integration Tests

Problem

VS Code reports "No packages found" for files with //go:build integration tags (e.g., backend/integration/coraza_integration_test.go). This is because gopls (the Go language server) does not include the integration build tag by default, causing it to ignore these files during analysis.

Solution

Configure gopls in the workspace settings to include the integration build tag.

Steps

1. Check `.vscode/settings.json`

Verify .vscode/settings.json exists. (Confirmed)

2. Update `gopls` settings

Edit .vscode/settings.json.
Locate the "gopls" configuration object.
Add or update the "buildFlags" property to include "-tags=integration".

Target Configuration:

"gopls": {
    "buildFlags": [
        "-tags=integration"
    ],
    // ... existing settings ...
}

3. Verification

Reload VS Code window (or restart the Go language server).
Open backend/integration/coraza_integration_test.go.
Verify that the "No packages found" error is resolved and IntelliSense works for the file.

1.1 KiB Raw Blame History