schema
This commit is contained in:
@@ -17,8 +17,8 @@ For commands that read such as grep or cat there is no need to ask for permissio
|
||||
Always use ide diagnostics to validate code changes when running with ide integration (goland, vscode)
|
||||
|
||||
|
||||
## linting all changes
|
||||
Also use `task lint` once you think you are done with edits to verify your changes have not caused other issues.
|
||||
## linting all edits after every change
|
||||
Always run `task lint` once you think you are done with edits to verify your changes have not caused other issues.
|
||||
When running `task lint` output should always be clean. 0 errors.
|
||||
Warnings about variable not set are ok.
|
||||
Lint output output must contain ‘Linting passed, A perfect score! well done!’ or you must fix an issue to resume.
|
||||
@@ -28,9 +28,9 @@ Use `task go:lint -- --fix` to fix go (file not formmatted) types of errors from
|
||||
## Essential Commands
|
||||
|
||||
### Development Setup
|
||||
- `devbox shell` - Enter development environment (Nix-based)
|
||||
- `devbox shell` - Enter development environment (Nix-based) I will start you already in the devbox shell for the project if there is one.
|
||||
- `touch .env` - Create environment variables file
|
||||
- `task fullsuite:ci` - Complete development workflow (generate, build, lint, test) This must pass clean or its not working.
|
||||
- `task fullsuite:ci` - Complete development workflow (generate, build, lint, test) This must pass clean or its not working. If its output has the word `FAIL` then investigate what the issue is before calling the change complete.
|
||||
|
||||
### Core Development Tasks
|
||||
- `task generate` - Generate all code (DB queries via SQLC, OpenAPI clients/servers, mocks, docs)
|
||||
|
||||
Reference in New Issue
Block a user