Fix formatting and type checks for OpenCode asset cache - #70
Merged
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
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.
Follow-up to #69: apply the plugin repository formatter and make the optional-key/cached-response branches explicit to pyright. No new cache layer, assertion relaxation, or behavior change.
Validation: pyright 0 errors; ruff check/format pass; real installed-OpenCode asset/ETag test passes. This corrects the pre-commit failure reported on the previous PR.
Summary by cubic
Applies the repository formatter to the OpenCode proxy and makes the optional-key/cached-response branches explicit to pyright. Fixes the pre-commit failure from the previous PR with no behavior change.
Written for commit 25070cb. Summary will update on new commits.