feat: make intents explicit in tempo() — remove implicit ChargeIntent default#22
Merged
brendanjryan merged 3 commits intomainfrom Feb 8, 2026
Merged
feat: make intents explicit in tempo() — remove implicit ChargeIntent default#22brendanjryan merged 3 commits intomainfrom
brendanjryan merged 3 commits intomainfrom
Conversation
… default
BREAKING CHANGE: tempo() now requires an explicit intents parameter.
Previously, tempo() silently injected a ChargeIntent as a default, making
it non-obvious which intents were active. Now callers must explicitly
opt into each intent:
# Before
method = tempo(account=account)
# After
method = tempo(account=account, intents={"charge": ChargeIntent()})
This makes the API surface explicit and removes the footgun where
additional intents passed via the intents dict were silently merged
with the hidden default.
brendanjryan
force-pushed
the
explicit-intents
branch
from
b18eaba to
7546b76
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Breaking Change
tempo()now requires an explicitintentsparameter. Previously it silently injected aChargeIntentas a default, making it non-obvious which intents were active.Before
After
Why
intents={"stream": StreamIntent(...)}silently merged with the hidden charge intentChanges
ChargeIntentinTempoMethod.__post_init__intentsa required parameter intempo()factory