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

SLVS-1777 Allow SonarQube for VS to be shown in the top-level menu #5986

Merged
merged 1 commit into from
Feb 7, 2025

Conversation

vnaskos-sonar
Copy link
Contributor

@vnaskos-sonar vnaskos-sonar commented Feb 4, 2025

Copy link

sonarqubecloud bot commented Feb 4, 2025

@@ -28,7 +28,7 @@

<Groups>
<Group guid="SonarLintCmdSet" id="SonarLintOuterGroup" priority="0x0100">
<Parent guid="guidSHLMainMenu" id="IDM_VS_MENU_EXTENSIONS" />
<Parent guid="guidSHLMainMenu" id="IDM_VS_TOOL_MAINMENU" />

Choose a reason for hiding this comment

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

What will be the default location if user installs the extension for the first time?

Choose a reason for hiding this comment

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

image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, by default it goes under the Extensions menu so the behavior remains unchanged with the previous SQVS versions. I tested this change on first and latest versions of VS and it seems to be working as expected.

@vnaskos-sonar vnaskos-sonar merged commit 504359b into master Feb 7, 2025
8 checks passed
@vnaskos-sonar vnaskos-sonar deleted the vn/sqvs-customizable-menu branch February 7, 2025 10:12
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.

2 participants