9.5 Type Generation Workflow [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.
====== 9.5 Type Generation Workflow ======

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

[[fxdemo:05-part:09-dds-idl-type-generation:start | Return to DDS / IDL / Type Generation ]]

The type generation [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflow]] should transform governed [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] source files into language-specific [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] implementation [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]]. Developers should run type generation through the approved script or documented command, not through undocumented local generator invocations.

The recommended Workflow is:

<code>
Architecture / Catalogue Definitions
        ↓
IDL Source Files
        ↓
Approved DDS Type Generator
        ↓
Language-Specific Generated Artifacts
        ↓
Node Implementation Uses Generated Types
        ↓
Runtime Topics Carry Typed Instances
</code>

The generation Workflow should identify:

  - IDL source files used as input.
  - DDS vendor or type-generation tool.
  - Generator version.
  - Target language or languages.
  - Output directory.
  - Command or script used to perform generation.
  - Expected generated Artifacts.
  - Validation checks run after generation.
  - [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] produced by the generation process, where applicable.

The team should route type generation through a script such as ''generateTypes'' when practical. The script should validate required inputs, check tool availability, write outputs to approved generated directories, and fail clearly when generation cannot complete.

----

<WRAP centeralign>

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

</WRAP>