-
Notifications
You must be signed in to change notification settings - Fork 2
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
auro-flightline: UI updates for canceled segment #6
Comments
This feature seems viable. I am assuming that @erikalanghauser is the design sponsor for this update? Is there a Figma link that can be attached to this issue? |
@blackfalcon - syncing up with Erica Breed tmrw to have her walk me through her proposed updates. Will report back here and add her Figma link if it's ready. |
I reviewed with Erica, the design update for the cancelled segment looks good to go. She is getting a github account created so that she can add her Figma here. Thanks! |
@geoffrich Signed-in. |
Here's the link for the cancelled flight component. Please reach out if you have any problems. Thanks. https://www.figma.com/file/929NVc0Q1bKwKIX299JbA3/Disruptions-Choice-Master-4e0c5a3?node-id=660%3A0 |
@geoffrich the design seems solid. For the API, I'd argue that this is a true boolean option, e.g. This is also consistent with the |
My only question there would be whether we anticipate displaying the flightline differently in other cases, e.g. delayed. If so, then we'd have three states -- unaffected, delayed, and cancelled. At that point is would make more sense as a string, no? A lot of features start out as one of two states, but expand as different variants are added. |
Outside the scope of this issue, we need to have solid guidelines for choosing a custom element's API type of attribute. Is It can be said that @erikalanghauser and @designingcircles I throw this back to you.
If this is a possibility, can we address that in the design now? |
@blackfalcon and @geoffrich. Given a flight it might have 4 statuses : unaffected, delayed, diverted and cancelled. In context for auro-flightline, only cancelled status matters as we are changing the colour of the line. If design wan't to come up with different color coding for delayed and diverted statuses then we have to make a new type called status. Otherwise we can stick to boolean state variable canceled. I'm inclined to make canceled as a boolean and make changes later if necessary. Please let me know if everyone is okay with this. |
Thanks for the feedback @SaiKarthikaT Here is what I am thinking. For the scope of this update and the reply from @SaiKarthikaT it is more clear that Regarding the auro-flight element, I would argue that the current boolean attributes are incorrect and really represent types of a flight stop. #35 If everyone is in agreement with that, I will update the scope of the work. |
@geoffrich is there a companion story in the future for auro-flight to address a canceled UI? Is there a badge or something that will accompany this color change to state CANCELED, something that screen readers will pick up on? |
@blackfalcon forgot to respond earlier. I don't think there are updates to auro-flight needed. The cancelled flight status will appear above the auro-flight component for screen readers to pick on. As far as I can tell, flight status is not currently within the scope of auro-flight. See the below screenshot: |
Is your feature request related to a problem? Please describe.
I want to show that a flight segment has been cancelled.
Describe the solution you'd like
The flightline will appear as a dashed red line when the segment has been cancelled.
Proposed design from Erica Breed (in disruptions context):
![image](https://user-images.githubusercontent.com/4992896/115746197-fc40a580-a348-11eb-9d9e-26f7e5893705.png)
Potential API (suggestions welcome):
Describe alternatives you've considered
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: