Skip to content

Commit 146c61b

Browse files
committed
no-mistakes(document): Fix stale entity-selection references in docs
1 parent 65c4ee2 commit 146c61b

2 files changed

Lines changed: 11 additions & 5 deletions

File tree

‎docs/features/metadata-dependencies.md‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -708,8 +708,11 @@ the snapshots first under `dep:<name>/<artifact>` source ids. It never writes ei
708708
POCO of a *value object* (and the shared enums it uses) that a generated type reaches — an entity
709709
or local value object that holds it, or a local template whose `@payloadRef` / `@responseRef` names
710710
it — because that generated type needs it to compile. `inScope` is Python's formula (no `matchesScope` on the
711-
project's own objects), and C# has no entity-name positional on `gen`, so the TypeScript
712-
"refuse an explicitly named imported object" check has no C# surface. Known edge: a local entity
711+
project's own objects). `dotnet meta gen --entities` resolves names against the in-scope
712+
objects only, so naming an excluded import is refused the way TypeScript's "refuse an
713+
explicitly named imported object" check refuses it (exit 2, `--entities names 'X', which
714+
matches no object in the metadata.` — C#'s wording, not TypeScript's imported-specific
715+
message). Known edge: a local entity
713716
that `extends` an imported concrete entity in a table-per-hierarchy mapping is not specially handled.
714717

715718
## Vendoring vs. depending

‎docs/features/own-your-codegen.md‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -591,7 +591,8 @@ handles those files by one rule:
591591

592592
- **Only a full run cleans up.** A run of the project's whole generator list decides; a run
593593
narrowed to some generators (`--generators`), to some entities (`meta gen <Entity>`,
594-
`metaobjects gen --entities`), or to a target that shares its directory with a target left
594+
`metaobjects gen --entities`, `dotnet meta gen --entities`, Maven `-Dmeta.entities`), or to
595+
a target that shares its directory with a target left
595596
out, deletes nothing, because the files of the part it skipped would all look stale. So
596597
does `--baseline=adopt`, which writes nothing by definition.
597598
- **A candidate is a file the manifest says `gen` wrote.** It lies under an output directory
@@ -612,8 +613,10 @@ handles those files by one rule:
612613
that name is not mistaken for generated output.
613614
- **A dry run** (`meta gen --dry-run`) reports what it would remove and removes nothing.
614615

615-
On **Java and Kotlin** every `mvn metaobjects:generate` execution is a full run, since its
616-
`<generators>` list is always complete. Every manifest entry names its owner: the generator's
616+
On **Java and Kotlin** every `mvn metaobjects:generate` execution runs the whole
617+
`<generators>` list, since there is no `--generators` narrowing; a run narrowed by
618+
`meta.entities` is the one exception, and it deletes no orphaned file (see
619+
[Select objects](../ports/java.md#generate) on the Java page). Every manifest entry names its owner: the generator's
617620
registry id and its output directory within the module, not the Maven execution, so
618621
`default-cli`, a renamed execution and the lifecycle execution agree. A recorded file no
619622
generator emitted in this build is an orphan when this run's own generators own it, or when

0 commit comments

Comments
 (0)