Skip to content

Commit 60bb5a5

Browse files
committed
describe compatibility option (#350)
1 parent d098772 commit 60bb5a5

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/modules/ROOT/pages/processor/configuration.adoc

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,7 @@ logging:
3939
compatibility:
4040
bean-validation-valid-on-reactive: false
4141
identifier-word-break-from-digit-to-letter: false
42+
identifier-prefix-invalid-enum-start: false
4243
4344
map:
4445
# java type mappings
@@ -526,6 +527,12 @@ keep the pre-2024.2 behavior. See xref:processor/identifier.adoc[Identifiers].
526527

527528
keep the pre-2024.2 behavior. See xref:processor/bean-validation.adoc[Bean Validation].
528529

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+
529536
== map:
530537

531538
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

Comments
 (0)