Press n or j to go to the next uncovered block, b, p or k for the previous block.
| 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 | import unchanged from '@feasibleone/blong'; import {handler} from '@feasibleone/blong'; /** * meta/db/db.ts — `e2e` schema/seed configuration. * * Declares the two tables (`e2e.widget`, `e2e.line`). No `dbTest` flag: whether * `meta/dbTest/*.yaml` is dispatched is the shared `srv.db` adapter's decision, whose `dev` and * `ci` activations turn it on and whose `upgrade` and `release` activations leave it off. A realm * that pins the flag here re-enables the test seeds in *every* intent — `upgrade` included, where * their handler groups are not loaded and the merge dies mid-migration (F-613). * No `mock` entries — the model uses the real DB * tables via the auto-bound CRUD handlers, which is what the tap and Playwright * tests exercise. * * `mock` is the server-side twin of the Storybook fixture: `mock: true` mocks * every model, and `mock: {<modelHandlerName>: true}` (a RegExp value matches * by name) makes the shared `srv.db` adapter serve those models from * `${subject}Fixture` data instead of the database. `demo/blong-marine` uses it * deliberately — coral is served by the database while family/species/habitat * are mocked — so both paths stay covered by one suite. The template omits it so * a scaffolded realm starts against real tables. */ export default handler(() => ({ config: { schema: { tables: {'e2e.widget': 1, 'e2e.line': 2, 'e2e.gadget': 2}, }, }, })); |