ID |
|
|---|---|
Status |
Backlog |
Bucket |
architecture |
Priority |
4 |
Theme |
classification-model |
Created |
2026-08-03 |
Updated |
2026-08-03 |
Clear the residual inaccuracies the @table-on-input deprecation reopen left behind
Reopening the @table-on-input deprecation window (accept, ignore, warn) left four
small residuals that the acceptance criterion did not reach, surfaced by the
In Review gate on that item. None is a behaviour bug and none blocked the gate, but
each is a live inaccuracy or dead code, so they are worth one tidy-up pass.
-
InputBeanResolver.java:40still carriesimport static no.sikt.graphitron.rewrite.BuildContext.DIR_TABLE;. It is the only remaining mention ofDIR_TABLEin that file: the nested-@tablerejection arm that read it was deleted, and Java does not error on an unused static import. Delete it. -
docs/manual/reference/directives/table.adoc, the first Constraints bullet: "Thenameparameter must resolve to a real jOOQ table; the generator fails the build with an unclassified-type error if the catalog has no matchingTableclass." That is now true only onOBJECT/INTERFACE. On an input the argument is never read, so an unresolvable name is inert (pinned byTableOnInputDeprecationWarningTest.unknownTableName_warnsAndIsOtherwiseInert). The deprecation admonition two sections up already says so, so the page is reconcilable in context, but the bullet reads unqualified. The multi-schema ambiguity bullet below it has the same scope problem. -
docs/manual/how-to/migrating-from-legacy.adoc:5: the intro’s four-category taxonomy still labels the WARN-today bucket "the synthesis shims (build succeeds with a WARN today, will fail later)". That bucket was retitled to== WARN today, error laterand now also holds@tableon input types, which is not a synthesis shim. The page’s:description:was reconciled; this sentence was not. -
~~Same page, the
== WARN today, error latersection opener points readers at a plan by slug, which the workflow’s user-facing-doc check calls out: a reader who arrived from search has noroadmap/directory.~~ Resolved by R473, which restated the opener as "no committed date" alone when it deleted the plan the pointer named.