Wiring
Page 8 of 8 · Decide

Five decisions are waiting for your answer

Every open question is here, with its context and options. Pick, add notes, then copy it all back in one go.

Q1Do the templates get generated wiring?
Context

The whole alcohol.zinc app was converted and behaves the same: same build, same tests, same data model. A new feature with a table then edits 1 shared file instead of 3, and a person edits none of them. Each template gets one piece we own: a source generator (.NET), a preload plug-in (Bun), a go generate step (Go) or a build_runner builder (Flutter).

Do we add generated wiring to the templates?

Pick one
Why we recommend B: .NET is the one language shown on a real app of yours. The honest scale check says the gain is modest (at most 2 of 94 merges clashed on these files), so use it for real once before owning four pieces of tooling. Bun is a close second, since its plug-in removed the watcher.
Q2What do we do about the .NET snapshot?
Context

EF needs the snapshot to write the next migration; without it, a new migration tried to create all 33 tables again. It clashes only when two pull requests change nearby parts of it; in alcohol.zinc's history it never clashed. On a clash, one command rebuilds it.

How do we handle the snapshot?

Pick one
Why we recommend A: It is one file, written by EF, with a one-command fix that only matters on a clash.
Q3Do we close the forgotten-migration gap in alcohol.zinc now?
Context

Today a model change without a migration passes CI (158 of 158 tests), and the migrator says "Successfully migrated". The column then does not exist, and a query that uses it fails. This has nothing to do with wiring; it is true today.

When do we add the CI check dotnet ef migrations has-pending-model-changes?

Pick one
Why we recommend A: It is one CI line, it already works on EF 8, and the gap exists today.
Q4Is the Bun release-build script acceptable?
Context

Bun's plug-ins work for run, test, watch and the build API, but the bun build command line cannot load one. So the Bun template's release build would run a 20-line tools/build.ts instead of the bun build command, with the same output.

Do we accept a build script in the Bun template?

Pick one
Why we recommend A: It is 20 lines with the same output, and run, test and watch need nothing.
Q5Do we test Windows too?
Context

Every result in this report ran on Linux. Windows was not tested in any language. Testing it needs a Windows runner, which needs spend on the GitHub budget.

Do we test generated wiring on Windows now?

Pick one
Why we recommend A: Nothing in the results depends on the operating system, and the first step is .NET on our own template.
+Anything else
Your comments

Comments from every page

Select text on any page, then right-click (or tap Comment). Remove any with ×. Only what is left here gets copied, and a copied comment is marked sent so it is never copied twice.

No comments yet.

Send it back

Copy your answers and comments back in one go

Preview of what gets copied