query-editor

To create Miroir Queries with TDD, you write tests for transformer definitions first, then implement the handleTransformer_<name> function, and finally register the transformer in core exports for runtime execution and build-time type generation.

Wiring a composite transformer into the Miroir runtime involves updating TransformerDefinition JSONs, implementing the handler function, and registering it in core exports to ensure proper build-time type generation and runtime execution across unit and integration phases.

TDD for library-implemented transformers in Miroir requires writing pre-flight tests, defining the expected behavior in tests before implementation, and then validating the transformer handler through both unit and integration tests.

Yes, updating TransformerDefinition JSONs is required when modifying a Miroir Query to define the behavior before implementing the handler and wiring it into the build process for type generation.

The best way to validate changes to Miroir Query transformers is to run both build and integration tests after registering the transformer in the runtime, ensuring the handler works correctly across all phases.

Using TDD precision when crafting Miroir Queries helps you define behavior before implementation, providing a repeatable path to create, modify, and validate queries with clear guidance for both library-implemented and composite transformers.