Guides

Describes the flow of source input and generation results for a watcher that started from actual development bottlenecks like duplicate API contracts, handler skeleton generation, and MongoDB field strings.

Each watcher started in different iterations

The Swagger watcher started from the issue of rewriting backend endpoints and DTOs as front contracts, while the Handler Generator began from the problem of creating class and method skeletons every time a router was added. Entity Fields were created to reduce string field and typo issues in MongoDB queries, and AsyncAPI extends the same automation flow to RSocket.

The guide explains not just a simple list of features, but how the source is read according to certain rules and what files it leads to. When the generation result differs from expectations, check the project path, package, and supported source patterns before runtime behavior.

Thematic guides

WatchForMainRun

Runs the initial execution of various development automation tasks and only reruns the necessary watchers when the source changes.

Swagger / OpenAPI

Generates API contracts for the frontend from already written RouterFunction, handlers, and DTOs in the backend.

Handler Generator

Generates and corrects repetitive class and method skeletons based on the handler references declared in the router.

Entity Fields

Creates enums to avoid repeating field and collection names as raw strings in MongoDB queries.

RSocket AsyncAPI

Applies the source-of-truth principle, like REST, to RSocket routes and payload types.

Project Defaults & Reload

Infers repetitive path settings in each project and connects changes in generated sources to the development restart flow.

External JAR & Type Mapping

Configures decompilation and schema mapping so that handlers and DTOs in common modules can also be used as the source of API contracts.

Troubleshooting

When generation results are missing, check the source pattern, package, path, and watcher scope in order.