Improved: "Go to Launchpad" button will be hidden in standalone mode and will be permission-driven (dxp/376)

[R-Sourabh]

Related Issues

hotwax/dxp-components#376

Short Description and Why It's Useful

• Go to Launchpad button will be hidden in standalone mode and will be permission-driven

Screenshots of Visual Changes before/after (If There Are Any)

Contribution and Currently Important Rules Acceptance

• I read and followed contribution rules

[gemini-code-assist]

Summary of Changes

Hello @R-Sourabh, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the user interface by implementing a permission-driven visibility control for the 'Go to Launchpad' button. It introduces a new authorization permission that, when combined with the application's standalone display mode, determines whether the button is shown to the user. This change enhances access control and provides a more tailored user experience within the application.

Highlights

• New Permission Introduced: A new authorization action, 'APP_PWA_STANDALONE_ACCESS', has been added to control access to specific features when the application is in standalone mode.
• Permission Mapping: The newly introduced 'APP_PWA_STANDALONE_ACCESS' permission is now mapped to the 'COMMON_ADMIN' role, ensuring that only users with this administrative role can access the associated functionality.
• Conditional Button Visibility: The 'Go to Launchpad' button in the Settings view is now conditionally hidden based on the 'APP_PWA_STANDALONE_ACCESS' permission and the application's display mode (standalone PWA). This ensures the button is only visible when appropriate.
• PWA Standalone Hiding Logic: CSS has been added to automatically hide any element with the 'standalone-hidden' attribute when the application is running in a Progressive Web App (PWA) standalone display mode.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a permission-driven visibility for the 'Go to Launchpad' button in standalone mode. The approach of adding a new action and rule is correct. However, there is a critical issue in Settings.vue where the imported hasPermission function and Actions object are not exposed to the template, which will cause a runtime error. I've also included suggestions to improve the implementation by following the best practice of using data- prefixed custom attributes for styling hooks.