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.

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

Removed getScopedKeybindingsForCommand (no references) #8283

Merged
merged 1 commit into from
Aug 6, 2020

Conversation

JonasHelming
Copy link
Contributor

fixes #8270

Signed-off-by: Jonas Helming jhelming@eclipsesource.com

What it does

PR removes an unreference function: getScopedKeybindingsForCommand (no updates since 3 years), see #8270 (comment)

By removing the function, #8270 is implicitly fixed

How to test

Nothing to test, removal, nothign should break, though

Review checklist

Reminder for reviewers

@vince-fugnitto vince-fugnitto added keybindings issues related to keybindings quality issues related to code and application quality labels Jul 31, 2020
Copy link
Member

@vince-fugnitto vince-fugnitto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good to me:

  • getScopedKeybindingsForCommand is currently unused (therefore it is untested during development)
  • getScopedKeybindingsForCommand is not tested (no unit tests)

Removing it seems the best course of action for code quality.


To be safe, we can add a breaking change entry in the changelog to advertise it has been removed.

@JonasHelming
Copy link
Contributor Author

The changes look good to me:

  • getScopedKeybindingsForCommand is currently unused (therefore it is untested during development)
  • getScopedKeybindingsForCommand is not tested (no unit tests)

Removing it seems the best course of action for code quality.

To be safe, we can add a breaking change entry in the changelog to advertise it has been removed.

I added the change log entry

@vince-fugnitto
Copy link
Member

@JonasHelming thank you for the contribution, I'll give others a chance to review or comment if they'd like and will likely merge next week if there are no objections 👍

@vince-fugnitto
Copy link
Member

@JonasHelming do you mind re-pushing (amend), travis seems to be in a weird state 👍

@vince-fugnitto
Copy link
Member

@JonasHelming can you rebase the pull-request so I can merge tomorrow?

@JonasHelming JonasHelming force-pushed the GH-8270 branch 4 times, most recently from 0fbf257 to 113a2c4 Compare August 5, 2020 13:42
@JonasHelming
Copy link
Contributor Author

@JonasHelming can you rebase the pull-request so I can merge tomorrow?

done

fixes eclipse-theia#8270

Signed-off-by: Jonas Helming <jhelming@eclipsesource.com>
@vince-fugnitto
Copy link
Member

vince-fugnitto commented Aug 6, 2020

@JonasHelming I rebased for you so as not to bother you :)
(I also updated the changelog as it was still referencing the prior release).

@JonasHelming
Copy link
Contributor Author

I actually already rebased it yesterday, maybe you merge soon, as the changelog change will probably run into conflicts almost every day :-)

@vince-fugnitto vince-fugnitto merged commit 63f23be into eclipse-theia:master Aug 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keybindings issues related to keybindings quality issues related to code and application quality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

KeybindingRegistry returns copies and original keybindings
2 participants