Skip to content

docs: clarify CORE schema octal compatibility configuration - #772

Merged
cowtowncoder merged 1 commit into
FasterXML:3.xfrom
wozhenbang2004:docs/core-schema-octal-feature
Nov 1, 2026
Merged

cowtowncoder merged 1 commit into
FasterXML:3.xfrom
wozhenbang2004:docs/core-schema-octal-feature

Conversation

@wozhenbang2004

Copy link
Copy Markdown
Contributor

Relates to #754.

Selecting YAMLSchema.CORE leaves PARSE_OCTAL_NUMBERS enabled for backwards compatibility, so 0444 still resolves to decimal 292. Clarify this at the CORE entry point and show the YAMLFactory configuration that disables the feature to read decimal 444. The behavior is already described on the read feature but is easy to miss when choosing a schema.

Documentation only. The existing ParseOctalNumbers276Test covers the documented enabled/disabled values and explicit 0o syntax. The full fork workflow (Maven verify) passed on Java 17, 21 and 25.

Validation: https://github.com/wozhenbang2004/jackson-dataformats-text/actions/runs/41316576291

Added documentation for CORE schema regarding octal number parsing.
@cowtowncoder
cowtowncoder merged commit 821a19c into FasterXML:3.x Nov 1, 2026
@cowtowncoder

Copy link
Copy Markdown
Member

Thank you, @wozhenbang2004 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants