Skip to content

fix: Preserve unknown API enum values - #301

Open
jonahe wants to merge 1 commit into
splunk:mainfrom
jonahe:codex/tolerate-unknown-api-enums
Open

jonahe wants to merge 1 commit into
splunk:mainfrom
jonahe:codex/tolerate-unknown-api-enums

Conversation

@jonahe

@jonahe jonahe commented Oct 30, 2026

Copy link
Copy Markdown

New server enum values can make successful API responses fail during
parsing, including project lookups with a capability_based creator role.
Preserve known enum members and carry unfamiliar values as raw strings
or integers so reading and serializing newer responses stays compatible.

Generate explicit enum-or-primitive field types while retaining
constants and explicitly closed enums. Keep collaborator roles and
generic providers usable, and report unsupported evaluator types instead
of guessing their implementation. No API changes are required.

New server enum values can make successful API responses fail during
parsing, including project lookups with a capability_based creator role.
Preserve known enum members and carry unfamiliar values as raw strings
or integers so reading and serializing newer responses stays compatible.

Generate explicit enum-or-primitive field types while retaining
constants and explicitly closed enums. Keep collaborator roles and
generic providers usable, and report unsupported evaluator types instead
of guessing their implementation. No API changes are required.
@github-actions

github-actions Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@jonahe

jonahe commented Oct 30, 2026

Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

@jonahe

jonahe commented Oct 30, 2026

Copy link
Copy Markdown
Author

recheck

This branch has not been deployed

No deployments
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.

1 participant