You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: relocate counter and rename queue messaging packages
Structural moves only — no behavior change.
- Relocate submitqueue/extension/counter -> extension/counter (generic
infrastructure belongs at the shared top level alongside the other
cross-domain extensions).
- Rename the messaging-transport packages entity/queue -> entity/messagequeue
and extension/queue -> extension/messagequeue (package `messagequeue`),
including the mysql impl, mock, ctl, and schema. "queue" was overloaded with
the submit queue (Request.Queue, QueueConfig); messagequeue disambiguates.
Repoints all import paths, converges call sites onto the entityqueue /
extqueue / queuemock / queueMySQL aliases (no bare `queue.` package ref
remains), moves the integration suites, and updates Makefile, CI targets, and
docs. Test compose contexts renamed to ext-counter-mysql / ext-messagequeue-sql.
## Test Plan
✅ make build, make test
✅ make gazelle / tidy / mocks clean
- **Test compose contexts**: the `testContext` passed to `NewComposeStack` (and thus the `sq-test-{context}-…` Docker project/container names) must be **domain-qualified** — `{category}-{domain}-{name}` where `{category}` is `svc`/`ext`/`core`/`e2e` and `{domain}` is `submitqueue`/`stovepipe`/… (omit the domain only for shared/cross-domain suites, e.g. `ext-queue-sql`). This keeps containers unambiguous and lets suites run in parallel. See [doc/howto/TESTING.md](doc/howto/TESTING.md#container-naming).
170
+
- **Test compose contexts**: the `testContext` passed to `NewComposeStack` (and thus the `sq-test-{context}-…` Docker project/container names) must be **domain-qualified** — `{category}-{domain}-{name}` where `{category}` is `svc`/`ext`/`core`/`e2e` and `{domain}` is `submitqueue`/`stovepipe`/… (omit the domain only for shared/cross-domain suites, e.g. `ext-messagequeue-sql`). This keeps containers unambiguous and lets suites run in parallel. See [doc/howto/TESTING.md](doc/howto/TESTING.md#container-naming).
171
171
- **README files**: Do not duplicate interface or type definitions as code blocks in READMEs. Describe behavior in prose and let readers navigate to the source. Only include code samples when explicitly instructed.
172
172
- **Markdown prose width**: Do not hard-wrap prose in Markdown docs (RFCs under `doc/`, READMEs). Write one line per paragraph and one line per list item, and let the editor soft-wrap — hard wrapping at a fixed column renders as a narrow fixed-width column regardless of window size. Code blocks, tables, and ASCII diagrams keep their own line breaks.
173
173
@@ -241,7 +241,7 @@ To create a mock package for a new extension (e.g., `submitqueue/extension/newex
241
241
3. Run `make mocks` to generate mock files into the new directory.
242
242
4. Run `make gazelle` to create the `BUILD.bazel` file automatically.
243
243
244
-
For inline mocks (mock in the same package, e.g., `extension/queue/mysql/mock_stores.go`):
244
+
For inline mocks (mock in the same package, e.g., `extension/messagequeue/mysql/mock_stores.go`):
245
245
246
246
1. Add a `//go:generate` directive with `-package=mypkg` and `-destination=mock_file.go`.
0 commit comments