Jasper
Jasper
When bundling a spec that has references to examples in json files some numbers that should appear as string are written as number. fi. the spec ``` properties: branchCode: maxLength:...
The readme of the maven plugin lists all the goals, but boat:doc is missing.
Using lombok in the generated sources does not make sense. Lombok value is to keep source code readable and compact by avoiding boiler-plate getters and setters. Generated code is not...
Both hiberate and jakarta `@Email` annotations are imported because of wildcard import statement, resulting in ``` [375,21] error: reference to Email is ambiguous [ERROR] both class org.hibernate.validator.constraints.Email in org.hibernate.validator.constraints and...
boat maven plugin doc goal has issues: - response schemas not shown - array query parameters show `]` as description - ...
`useSetForUniqueItems` is now ignored, but still listed in README and referenced in header comment generated for some classes. the value is always empty. To ignore confusion, the references should be...
_This issue occurs when the first schema is defined in a "common" spec, or is an existing class, and a second spec refers to the previously generated class using `schemaMapping'_...
In case of nested class the datatype might be: `com.org.package.MyType.MyNestedType`. In such case the packageName will be `com.org.package.MyType` _Originally posted by @walaniam in https://github.com/Backbase/backbase-openapi-tools/pull/632#discussion_r1321536035_
The default value should be `target/boat-radio-report/radioOutput.json` ``` [INFO] UPLOAD TO BOAT-BAY SUCCESSFUL, check the full report: /Users/jasper/git/paym/payment-order-presentation-spec/target/target/boat-radio-report/radioOutput.json ```