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

View menu text scrub #1053

Closed
wants to merge 1 commit into from
Closed

View menu text scrub #1053

wants to merge 1 commit into from

Conversation

corinagum
Copy link
Contributor

image

Resolves #820

(Low priority PR as this is a 4.2 change)

@corinagum corinagum changed the base branch from master to v4 October 29, 2018 22:06
@coveralls
Copy link

Pull Request Test Coverage Report for Build 1145

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.01%) to 53.459%

Totals Coverage Status
Change from base Build 1126: 0.01%
Covered Lines: 4224
Relevant Lines: 7125

💛 - Coveralls

@@ -235,16 +235,7 @@ export const AppMenuBuilder = new class AppMenuBuilderImpl implements AppMenuBui
return {
label: 'View',
submenu: [
{
label: 'Explorer',
click: () => mainWindow.commandService.remoteCall(SharedConstants.Commands.UI.ShowExplorer)
Copy link
Contributor

Choose a reason for hiding this comment

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

Are there any more calls to these commands? If not, let's remove the command registrations too.

@@ -3,20 +3,20 @@
object-assign
Copy link
Contributor

Choose a reason for hiding this comment

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

How did this get in there?

Copy link
Contributor

Choose a reason for hiding this comment

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

This diff was showing up for me as well every time I pulled and rebuilt the package, but I never checked it in. This must be that same change. I have no idea how it gets generated though.

@tonyanziano
Copy link
Contributor

Also, once you resolve all the changes you might want to re-submit this PR into master instead of v4 as that is the new default working branch.

@corinagum
Copy link
Contributor Author

@tonyanziano @justinwilaby Thanks guys, let me redo this PR with corrections. :)

@corinagum
Copy link
Contributor Author

Closing this in favor of #1061

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants