13.7 generateTypes [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 13.7 generateTypes ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:13-build-and-run-scripts:start | Return to Build and Run Scripts ]]

The ''generateTypes'' script or command should generate [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]]/[[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]]-derived type [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] from approved IDL source files. It should provide the controlled path from governed IDL definitions to generated implementation Artifacts.

The script should:

  - Locate approved IDL source files.
  - Validate required DDS tooling and generator availability.
  - Identify the selected DDS product or products.
  - Identify target language or languages.
  - Write generated outputs to the approved generated directories.
  - Avoid overwriting handwritten source files.
  - Produce a manifest or diagnostic output identifying generated Artifacts.
  - Run validation checks after generation where practical.
  - Return a non-zero exit code when generation fails.
  - Record [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] when generation forms part of acceptance.

If the phase supports multiple DDS vendors, ''generateTypes'' should either support product-specific generation options or call product-specific generation scripts through a documented wrapper. The generated output structure should keep vendor-specific and language-specific Artifacts separate.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>