You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The lounge team would like a Club 49 badge. Very similar to the existing oneworld, lounge, and mileage plan badge but with an icon included.
Describe the solution you'd like
Ideally a user can follow the same process that we have established for oneworld, lounge and mileage plan badges and style the icon by the same auro-badge attribute. Currently a user can achieve this using a custom badge but they would also need to customize the icon color to match because the icon is not included in the badge repo.
Describe alternatives you've considered
Lounge teams builds a web component in the component hangar for 'Guest badges' that is just a wrapper that implements standard auro-badge customizations for our Alaska tier badges, oneworld tier badges, Club 49 badge(new) , Lounge & Lounge+
Is your feature request related to a problem? Please describe.
The lounge team would like a Club 49 badge. Very similar to the existing oneworld, lounge, and mileage plan badge but with an icon included.
Describe the solution you'd like
Ideally a user can follow the same process that we have established for oneworld, lounge and mileage plan badges and style the icon by the same auro-badge attribute. Currently a user can achieve this using a custom badge but they would also need to customize the icon color to match because the icon is not included in the badge repo.
Describe alternatives you've considered
Club 49:
Figma for our current work:
https://www.figma.com/file/InsfVhuoqSJi85TXXfWykN/Lounge-In---Scan-entry?node-id=2654%3A8709&t=yakjPvJHZzgiXzgq-1
One place these customizations are already implemented by another team: [Awards balance box Hangar Component]
](https://components.alaskaair.com/catelog/demo/awards-balance-box)
Additional Context
This is a spin off of #41 the other asks for that initial feature have been implemented in #75 or will be implemented in #96
The text was updated successfully, but these errors were encountered: