Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Shouldn't TextDocumentChangeEvent.reason<TextDocumentChangeReason> include Paste and Cut? #204018

Closed
kedicesur opened this issue Feb 1, 2024 · 3 comments
Closed

Shouldn't TextDocumentChangeEvent.reason<TextDocumentChangeReason> include Paste and Cut? #204018

kedicesur opened this issue Feb 1, 2024 · 3 comments
Assignees
@mjbvz
Labels
api feature-request Request for new features or functionality
Milestone
Backlog Candidates

Comments

@kedicesur
Copy link

kedicesur commented Feb 1, 2024 •
edited

type: feature request / enhancement
The reason property only enumerates Undo and Redo however i think it's essential to know Paste and even Cut or even API as well. At the moment i am trying to figure out how to safely distinguish a paste from a keyboard input. One can paste a single character or even a keypress may yield multiple characters such as an enabled autoClosingBrackets would result "{}" etc...
@VSCodeTriageBot VSCodeTriageBot added the stale Issues that have not been triaged in an appropriate amount of time label Feb 8, 2024
@connor4312 connor4312 assigned mjbvz and unassigned connor4312 and hediet Feb 8, 2024
@VSCodeTriageBot VSCodeTriageBot removed triage-needed stale Issues that have not been triaged in an appropriate amount of time labels Feb 8, 2024
@mjbvz mjbvz added feature-request Request for new features or functionality api labels Feb 8, 2024
@VSCodeTriageBot VSCodeTriageBot added this to the Backlog Candidates milestone Feb 8, 2024
@VSCodeTriageBot
Copy link
Collaborator

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@Number-3434 Number-3434 mentioned this issue Mar 13, 2024
Open
@VSCodeTriageBot
Copy link
Collaborator

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@VSCodeTriageBot
Copy link
Collaborator

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@VSCodeTriageBot VSCodeTriageBot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mjbvz mjbvz

Labels
api feature-request Request for new features or functionality
Projects
None yet
Milestone
Backlog Candidates
Development

No branches or pull requests
5 participants
@connor4312 @hediet @kedicesur @mjbvz @VSCodeTriageBot