Repository navigation
chore(deps): update opencode host runtime - #16
Merged
Merged
Conversation
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
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.
This PR contains the following updates:
0.8.3→0.8.40.8.3→0.8.41.9.18→1.9.19Release Notes
anomalyco/opentui (@opentui/core)
v0.8.4Compare Source
A chat log often puts many
CodeRenderableblocks in aScrollBoxRenderablewithviewportCulling: true. Withstreaming: trueanddrawUnstyledText: false, a block that gets new content keeps showing its old highlighted text until the new highlight is ready, so the reader never sees a flash of plain text. But a block starts its highlight from its update hook, and a frame calls no hooks on a block that the scroll box culls. In 0.8.3, a culled block therefore kept its old text in its buffer, and layout measured that old text. The scroll box reported a stalescrollHeightuntil the block scrolled back into view.In 0.8.4, a block that gets new content first asks the scene whether the hooks of the next frame reach it. If they do, the block keeps its old highlight, as before. If they do not, as for a culled, hidden, or detached block, the block loads the new plain text at once, so layout measures the new content. It does not paint that text until the highlight is ready. The highlight starts in the first frame that reaches the block again. C hosts can ask the same question with
ot_scene_reaches_hooks. It answers with the branch selection that the next frame uses.Added
ot_scene_reaches_hookstells if the hooks of a frame reach a node. It selects culled branches as the next frame does. See C.Fixed
CodeRenderablewithdrawUnstyledText: falsenow measures new content immediately. It does not paint that text until its highlight is ready. See Code.API changes and documentation: https://opentui.com/docs/releases/0.8.4
Full Changelog: anomalyco/opentui@v0.8.3...v0.8.4
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.