Skip to content

fix(webui): align extension page snackbars#6973

Closed
1zzxy1 wants to merge 1 commit intoAstrBotDevs:masterfrom
1zzxy1:fix/extension-snackbar-alignment
Closed

fix(webui): align extension page snackbars#6973
1zzxy1 wants to merge 1 commit intoAstrBotDevs:masterfrom
1zzxy1:fix/extension-snackbar-alignment

Conversation

@1zzxy1
Copy link
Copy Markdown
Contributor

@1zzxy1 1zzxy1 commented Mar 26, 2026

Summary

  • align the Extension page snackbar position with the app's shared toast convention
  • show install/update/uninstall result messages at top center instead of the default bottom position
  • keep the fix limited to the local Extension page snackbar without changing existing install logic

Fixes #6022

Testing

  • git diff --check
  • frontend build/lint not run locally in this environment (dashboard dependencies/pnpm unavailable)

Summary by Sourcery

Enhancements:

  • Update the extension page snackbar to display at the top center to match global toast positioning.

@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Mar 26, 2026
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 standardizes the display of notification snackbars on the Extension page. It improves user experience by ensuring consistency with the application's overall UI conventions for displaying transient messages, specifically by centralizing success/failure notifications.

Highlights

  • Snackbar Alignment: Aligned the snackbar position on the Extension page to match the application's shared toast convention.
  • Notification Placement: Changed install/update/uninstall result messages to display at the top center instead of the default bottom position.
  • Scope Limitation: Ensured the fix is limited to the local Extension page snackbar without altering existing installation logic.
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.

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.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • Since this change is meant to align with a shared toast convention, consider centralizing the snackbar location in a shared component or config instead of setting it only on this page to avoid future divergence.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Since this change is meant to align with a shared toast convention, consider centralizing the snackbar location in a shared component or config instead of setting it only on this page to avoid future divergence.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@dosubot dosubot Bot added the area:webui The bug / feature is about webui(dashboard) of astrbot. label Mar 26, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request modifies the ExtensionPage.vue file to add a location="top center" attribute to the <v-snackbar> component. There are no review comments to provide feedback on.

@Soulter Soulter closed this Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:webui The bug / feature is about webui(dashboard) of astrbot. size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]弹窗和提示不对齐

2 participants