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

Notification tray for displaying in-flight requests #12078

Open
wants to merge 29 commits into
base: develop
Choose a base branch
from

Conversation

somebody1234
Copy link
Contributor

Pull Request Description

Important Notes

  • This PR uses useIsMutating to find mutation state. It's possible to use useIsFetching to also display query state - however "list directory" background refetching would cause constant notifications.
  • UI is a placeholder - it does not need to be a notification tray, the important part of this PR is the new hook to return the state of all in-flight mutations.

Testing Instructions

  • Do all mutation types (delete, rename, copy, move, undelete, force delete, clear trash)
  • Open notification tray
  • Check for notification
    • The notification may have disappeared if the mutation has completed - this is intentional as the notifications are not meant to be permanent.

Further Improvements

  • Display red "unread notifications" badge when new notifications are in flight
  • Consider creating permanent notification objects instead, which include a timestamp, and are (possibly) preserved indefinitely
    • If the user is (e.g.) uploading or deleting a lot of assets though, it would clutter up the notification tray if/unless notifications caused by mutations are collapsed.
    • Notifications do not exist server side, so they are not preserved across sessions. This is fine, but we might want to have a log of mutations on the server side eventually.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

  • The documentation has been updated, if necessary.
  • Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
  • All code follows the
    Scala,
    Java,
    TypeScript,
    and
    Rust
    style guides. In case you are using a language not listed above, follow the Rust style guide.
  • Unit tests have been written where possible.
  • If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
    or the Snowflake database integration, a run of the Extra Tests has been scheduled.
    • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

@somebody1234 somebody1234 added CI: No changelog needed Do not require a changelog entry for this PR. x-new-feature Type: new feature request g-dashboard labels Jan 19, 2025
Copy link

github-actions bot commented Jan 19, 2025

🧪 Storybook is successfully deployed!

📊 Dashboard:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: No changelog needed Do not require a changelog entry for this PR. g-dashboard x-new-feature Type: new feature request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant