Include cost in v2 usage_update
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start in src/protocols/acp/v2.rs and compare its usage_update emitter with the v1 usage_update implementation to identify the existing cost source. Update the v2 output so it includes cost alongside used and size, then verify that v2 usage_update carries the same cost as v1.
Written by the indexing model from the issue text.
Description
v1 usage_update carries cost; the v2 emitter in src/protocols/acp/v2.rs sends only used and size. Populate cost in v2 from the same source.
Part of #146.
- Dominant language
- Rust
- Stars
- 40
- Forks
- 4
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 148
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from speakeasy-api/kit
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
speakeasy-api/kit#175 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
speakeasy-api/kit#165 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
speakeasy-api/kit#149 ·
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 84/100
speakeasy-api/kit#148 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 1/100
speakeasy-api/kit#235 ·
All issues in speakeasy-api/kit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100