This repository was archived by the owner on Jan 10, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 147
This repository was archived by the owner on Jan 10, 2026. It is now read-only.
Updating Transplanting Report with new BannerComponent #641
Copy link
Copy link
Open
Labels
Good Second IssueIssue that is a little deeper than a Good First Issue.Issue that is a little deeper than a Good First Issue.ReservedIssue created and reserved for use in a course.Issue created and reserved for use in a course.UI/UXUser Interface / User Experience ImprovementUser Interface / User Experience ImprovementenhancementImprovement to the projectImprovement to the project
Description
Desired Design
Currently the Transplanting Report still makes use of the ErrorBannerComponent. However, the merging of #622 means that these instances need to be removed and the page adequately updated with new data variables to handle the newer BannerComponent.
It's also necessary to consider what new constants need to be added to the BannerMessageConstants.js specifically for the Transplanting Report.
Here are the necessary changes to complete this issue:
- First and foremost: have a conversation about what new features would be appreciated. For example: success banner when a banner is successfully updated. A message banner to inform the user that an edit was canceled. A danger banner to indicate a log didn't successfully save and to try again later. These are but a few examples.
- Should the banner be closed by pressing an 'X' or should it be timeout based? Whatever is decided should be consistent in all pages,
- Remove the
ErrorBannerComponentfrom the page. - Import the
BannerComponentinto the page (simply add it to the Vue instance in the page). - Add the necessary data variables to support
- Update pre-existing functions to make the
BannerComponentvisible, give the correct object, and handle visibility changes. - Implement any new features that arise during conversation.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Good Second IssueIssue that is a little deeper than a Good First Issue.Issue that is a little deeper than a Good First Issue.ReservedIssue created and reserved for use in a course.Issue created and reserved for use in a course.UI/UXUser Interface / User Experience ImprovementUser Interface / User Experience ImprovementenhancementImprovement to the projectImprovement to the project