-
Notifications
You must be signed in to change notification settings - Fork 405
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
Add a Global status bar in API Dash #587
Comments
Hi, can you assign us this issue for our team in FOSSHACK 2025 |
@ak7cr Kindly read - https://github.com/foss42/apidash/blob/main/CONTRIBUTING.md#why-we-do-not-assign-issues-to-anyone |
Hi @ashitaprasad could you please draw a mockup of some sorts on what you have in mind for "A Status bar at the bottom of the request details pane". Is it somekind of notification center or a console log? |
@WrathOP The reason I have not posted any mock-up as it will introduce bias and contributors will start implementing the same. Designing the UI is also part of the issue so please feel free to post any feature mockups. It is neither a notification center (where usually push notifications stack up) or a console log (which is a nice idea). Initially the idea is to have a place at the bottom of the request details pane which dynamically updates based on the the selected request when the request does not pass a set of asserts. But, the feature scope is still open for further exploration. |
I'm considering using MaterialBanner to help facilitate this use case - https://api.flutter.dev/flutter/material/MaterialBanner-class.html but it has one limitation , it's attached to AppBar from a placement perspective. |
@swapnildey94 material Banner will not work in this case as:
|
API Dash currently does not have a mechanism to notify users of any issue in their requests. Toast notifications are shown for some actions, but they are not permanent.
A Status bar at the bottom of the request details pane, can be utilized to notify users whenever certain request checks fail like:
The text was updated successfully, but these errors were encountered: