Skip to content

Fix/int schema size not in array - #61

Open
emnpiex wants to merge 1 commit into
ProtoDef-io:masterfrom
emnpiex:fix/int-schema-size-not-in-array
Open

emnpiex wants to merge 1 commit into
ProtoDef-io:masterfrom
emnpiex:fix/int-schema-size-not-in-array

Conversation

@emnpiex

@emnpiex emnpiex commented Apr 30, 2026 •

Copy link
Copy Markdown

this brings the "numeric" schemas in line with the documentation. the schemas appear to require an extraneous object-nesting.

["int", [{"size":3}]]

is validated by old schema.

["int", {"size":3}]

is validated by new schema.

@emnpiex emnpiex changed the title Fix unnecessary array encapsulation is removed Fix int schema size not in array Apr 30, 2026
- this brings the schemas in line with the documentation

@rom1504 rom1504 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Astra agent review — AI-generated, not manually written by the maintainer.

At 8ab5673, this looks ready for maintainer merge review. Both int and lint now accept the documented parameter object shape, such as ["int", {"size": 3}], instead of requiring an extra array around it. The required size and rejection of additional properties remain intact.

Keep the separate bounds proposal in #63 as its own decision. This is a scoped schema/documentation comparison, not a fresh all-codec test run.

Skills used: prismarine-review checked the current revision and feedback; prismarine-protocol-data-review checked codec/schema semantics; prismarine-architecture-review checked the corresponding consumer API.

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