Rerender notebook when output settings change
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start at the useNotebookOptions hook described in the issue and reproduce the behavior by changing notebook.output.scrolling with the notebook and Settings open side by side. Trace how the mutable options state is observed, then verify that the notebook rerenders with the updated setting and that the reproduction steps no longer fail.
Written by the indexing model from the issue text.
Description
System details:
Positron and OS details:
Positron Version: 2026.04.0 build 61
Code - OSS Version: 1.108.0
Commit: 5bdd1a01b6009b0d53ca6e261ff76bfed2e94bfd
Date: 2026-03-06T07:39:52.911Z
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.3.0
Describe the issue:
Notebook does not automatically rerender when output settings change. This is because the useNotebookOptions hook uses state that is a mutable object whose reference never changes.
Steps to reproduce the issue:
- Open a notebook.
- Open settings in a side-by-side pane - this is necessary otherwise the notebook will just rerender when swapping tabs.
- Change a notebook option setting e.g.
notebook.output.scrolling. - Verify that the notebook rerendered with the new setting value - FAIL
Were there any error messages in the UI, Output panel, or Developer Tools console?
Nope.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Contributor guide
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 posit-dev/positron
-
ci-cd lang: python
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
area: quarto lang: r
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area: quarto lang: r
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
area: onboarding area: welcome enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area: assistant bug support
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
All issues in posit-dev/positron
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·