[WIP] isWithinTokenLimit Throws Error on Special Characters #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
isWithinTokenLimit
doesn't support special character handling likecountTokens
doescountTokens
acceptsEncodeOptions
butisWithinTokenLimit
doesn'tisWithinTokenLimit
method signature to accept optionalEncodeOptions
parameterencodeChatGenerator
to accept and pass throughEncodeOptions
parametercountTokens
method for chat messagesSummary
Successfully implemented support for special tokens in
isWithinTokenLimit
method. The changes are minimal and fully backward-compatible:Changes Made:
encodeOptions?: EncodeOptions
parameter toisWithinTokenLimit
methodencodeChatGenerator
to accept and pass through encode optionscountTokens
where encode options weren't passed to chat generatorUsage Examples:
The implementation is consistent with
countTokens
behavior and maintains full backward compatibility.Fixes #74.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.