posit-dev / posit-dev/positron
Add a setting that controls whether "Open in editor" in the Console turns output into comments.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 206
Description
System details:
Positron and OS details:
Positron after #6912 is merged.
Interpreter details:
R or Python.
Describe the issue:
Add a setting that controls whether "Open in editor" in the Console turns output into comments.
(See: #6940)
Steps to reproduce the issue:
- Execute some code that produces output in the Console. It can be R or Python code. Either is fine.
For example:
- Use the "Open in editor" button on the Console action bar to open the console in an Editor.
You will see the following in the newly-opened Editor:
Note that the code appears as code and the output appears as comments.
Some people might not like the output appearing as comments. We should add a setting that allows users decide whether they want the output to appear as comments.
Expected or desired behavior:
- N/A
Were there any error messages in the UI, Output panel, or Developer Tools console?
- N/A
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.
Research direction
Start by tracing the Console's "Open in editor" action and the settings entry points it uses; the issue does not name specific files or tests. Done means users can choose whether console output is inserted as comments when opening the Console in an Editor, for both R and Python.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, r, typescript
- Domain
- desktop, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100