You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/modules/ROOT/pages/processor/configuration.adoc
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,7 @@ logging:
39
39
compatibility:
40
40
bean-validation-valid-on-reactive: false
41
41
identifier-word-break-from-digit-to-letter: false
42
+
identifier-prefix-invalid-enum-start: false
42
43
43
44
map:
44
45
# java type mappings
@@ -526,6 +527,12 @@ keep the pre-2024.2 behavior. See xref:processor/identifier.adoc[Identifiers].
526
527
527
528
keep the pre-2024.2 behavior. See xref:processor/bean-validation.adoc[Bean Validation].
528
529
530
+
=== identifier-prefix-invalid-enum-start
531
+
532
+
**optional** (boolean, `true` or `false`, default is `true`)
533
+
534
+
*Invalid characters* (e.g. numbers or underscore) at the start of enum values are prefixed with `"V"` (for value) to generate valid java identifiers. The old behaviour (pre-2025.4.1) was to strip the invalid start characters.
535
+
529
536
== map:
530
537
531
538
Using type mapping, we can tell the processor to map types (schemas) from an `openapi.yaml` description to a specific existing java type instead of generating a model class from the source OpenAPI type.
0 commit comments