Skip to content

Allow custom extension ID for Intercode issuing (e.g. +FRII1) - #17

Merged
chtitux merged 2 commits into
mainfrom
claude/fix-extension-id-verification-wHgBj
Feb 15, 2026
Merged

Allow custom extension ID for Intercode issuing (e.g. +FRII1)#17
chtitux merged 2 commits into
mainfrom
claude/fix-extension-id-verification-wHgBj

Conversation

@chtitux

@chtitux chtitux commented Feb 15, 2026

Copy link
Copy Markdown
Contributor

The encoder previously hardcoded the extension ID as _<RICS>II1. This adds an optional extensionId field to IntercodeIssuingDataInput so callers can pass the string as-is (e.g. +FRII1 for country-code variant) instead of always deriving it from a numeric RICS code.

https://claude.ai/code/session_018mxZQ6pZkHoU8xHgxNkDKt

The encoder previously hardcoded the extension ID as `_<RICS>II1`.
This adds an optional `extensionId` field to `IntercodeIssuingDataInput`
so callers can pass the string as-is (e.g. `+FRII1` for country-code
variant) instead of always deriving it from a numeric RICS code.

https://claude.ai/code/session_018mxZQ6pZkHoU8xHgxNkDKt
The decoder now stores the original extensionId string (e.g. "+FRII1")
on IntercodeIssuingData so it survives the decode → input → encode
cycle. Both decodedToInput (tests) and ticketToInput (website) now
propagate the field to the encoder input.

https://claude.ai/code/session_018mxZQ6pZkHoU8xHgxNkDKt
@chtitux
chtitux merged commit 0d7fd82 into main Feb 15, 2026
4 checks passed
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