-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
277 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,4 +13,4 @@ uploads | |
modules/core/presentation/assets/css/main.min.css | ||
bin/ | ||
logs/ | ||
migrations/ | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# CLAUDE.md - IOTA SDK Guide | ||
|
||
## Build/Lint/Test Commands | ||
- Build app: `make generate && make css` | ||
- Run all tests: `make test` or `go test -v ./...` | ||
- Run single test: `go test -v ./path/to/package -run TestName` | ||
- Run specific subtest: `go test -v ./path/to/package -run TestName/SubtestName` | ||
- Lint code: `make lint` or `golangci-lint run ./...` | ||
- JSON linting: `make build-iota-linter && make run-iota-linter` | ||
- Apply migrations: `make migrate up` | ||
|
||
## Code Style Guidelines | ||
- Use Go v1.23.2 and follow standard Go idioms | ||
- File organization: group related functionality in modules/ or pkg/ directories | ||
- Naming: use camelCase for variables, PascalCase for exported functions/types | ||
- Testing: table-driven tests with descriptive names (TestFunctionName_Scenario) | ||
- Error handling: use pkg/serrors for standard error types | ||
- Type safety: use strong typing and avoid interface{} where possible | ||
- Use the functional programming utilities in pkg/fp/ for collections | ||
- Follow existing patterns for database operations with jmoiron/sqlx | ||
- For UI components, follow the existing templ/htmx patterns |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.