Skip to content

feat: mark the standard bot tokens as handle types - #17

Merged
NenkaLab merged 1 commit into
masterfrom
feat/handle-token-fields
Nov 4, 2026
Merged

NenkaLab merged 1 commit into
masterfrom
feat/handle-token-fields

Conversation

@NenkaLab

@NenkaLab NenkaLab commented Nov 4, 2026

Copy link
Copy Markdown
Member

What changed

The standard bot module declares its tokens with the new handle type: replyToken as handle<reply>, readToken as handle<read>, image and author.avatar as handle<image>, and the token parameter of reply, markRead and image to match.

A provider written before this declares its tokens as string. So fits accepts a string where the standard has a handle, and such providers keep working.

Why

The host finds the token fields it must wrap from a hard-coded list. With the spec naming them, a later change can read the fields from the spec, so a provider that adds a token field gets the same protection without a host change.

Testing

:contract:test and :tck:test pass. New tests cover the fit rule (a string fits a handle, an int and a different kind do not) and that the standard module marks its tokens.

@NenkaLab
NenkaLab merged commit 9c50942 into master Nov 4, 2026
1 check 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.

1 participant