massive fixes to stores and addresses
This commit is contained in:
46
CLAUDE.md
46
CLAUDE.md
@@ -30,6 +30,49 @@ Before writing any code:
|
||||
|
||||
4. Run verification and iterate until it passes
|
||||
|
||||
## Git Bash / MSYS Path Conversion Issue (Windows Host)
|
||||
|
||||
**CRITICAL ISSUE**: Git Bash on Windows automatically converts Unix-style paths to Windows paths, which breaks Podman/Docker commands.
|
||||
|
||||
### Problem Examples:
|
||||
|
||||
```bash
|
||||
# This FAILS in Git Bash:
|
||||
podman exec container /usr/local/bin/script.sh
|
||||
# Git Bash converts to: C:/Program Files/Git/usr/local/bin/script.sh
|
||||
|
||||
# This FAILS in Git Bash:
|
||||
podman exec container bash -c "cat /tmp/file.sql"
|
||||
# Git Bash converts /tmp to C:/Users/user/AppData/Local/Temp
|
||||
```
|
||||
|
||||
### Solutions:
|
||||
|
||||
1. **Use `sh -c` instead of `bash -c`** for single-quoted commands:
|
||||
|
||||
```bash
|
||||
podman exec container sh -c '/usr/local/bin/script.sh'
|
||||
```
|
||||
|
||||
2. **Use double slashes** to escape path conversion:
|
||||
|
||||
```bash
|
||||
podman exec container //usr//local//bin//script.sh
|
||||
```
|
||||
|
||||
3. **Set MSYS_NO_PATHCONV** environment variable:
|
||||
|
||||
```bash
|
||||
MSYS_NO_PATHCONV=1 podman exec container /usr/local/bin/script.sh
|
||||
```
|
||||
|
||||
4. **Use Windows paths with forward slashes** when referencing host files:
|
||||
```bash
|
||||
podman cp "d:/path/to/file" container:/tmp/file
|
||||
```
|
||||
|
||||
**ALWAYS use one of these workarounds when running Bash commands on Windows that involve Unix paths inside containers.**
|
||||
|
||||
## Communication Style: Ask Before Assuming
|
||||
|
||||
**IMPORTANT**: When helping with tasks, **ask clarifying questions before making assumptions**. Do not assume:
|
||||
@@ -57,6 +100,9 @@ When instructions say "run in dev" or "run in the dev container", they mean exec
|
||||
1. **ALL tests MUST be executed in the dev container** - the Linux container environment
|
||||
2. **NEVER run tests directly on Windows host** - test results from Windows are unreliable
|
||||
3. **Always use the dev container for testing** when developing on Windows
|
||||
4. **TypeScript type-check MUST run in dev container** - `npm run type-check` on Windows does not reliably detect errors
|
||||
|
||||
See [docs/TESTING.md](docs/TESTING.md) for comprehensive testing documentation.
|
||||
|
||||
### How to Run Tests Correctly
|
||||
|
||||
|
||||
Reference in New Issue
Block a user