Implement accordion design and functionality

[jordanjones243]

Alaska Airlines Pull Request

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes: #85, #86

Summary:

Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.

Type of change:

Please delete options that are not relevant.

• [x] New capability
• [x] Revision of an existing capability
• [ ] Infrastructure change (automation, etc.)
• [ ] Other (please elaborate)

Checklist:

• [x] My update follows the CONTRIBUTING guidelines of this project
• [x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.

Thank you for your submission!
-- Auro Design System Team

[github-actions[bot]]

Surge demo deployment succeeded! 🚀🚀🚀

Auro Web Component Generator

[CLAassistant]

All committers have signed the CLA.

[blackfalcon]

Surge demo deployment failed! 😭

This failed because the location of the resource was moved in this commit

• https://github.com/AlaskaAirlines/auro-library/pull/34/files#diff-404055b8772c0e4473fbdb0b6bb209ca2d556d45300da9adb3d94262f4a3e568

See issue

• https://github.com/AlaskaAirlines/auro-library/issues/38

[blackfalcon]

@jordanjones243 Please update all relevant commits with the issue ID the commit is addressing.

[blackfalcon]

@jordanjones243 why is the previous chore release commit rebased into this feature branch? We can't merge that into main that way.

[jordanjones243]

Noticed something else while reviewing the UI. You have a border that is applied on focus but it's only there on focus. This causes a small layout shift on focus. You should have a transparent border on the element 100% of the time and just change it to blue when focus occurs. This will prevent the layout shift.

Additionally, if I click the chevron portion of the trigger the focus border becomes persistent on the trigger. If I click the text portion of the trigger the focus border does not appear. I don't think clicking should apply the border in either case.

Resolved.

[blackfalcon]

@jordanjones243 looking at this PR I also noticed that the .npmignore file is not configured correctly. It is still using the legacy version. Please review the generator for the correct configuration.

[jordanjones243]

@jordanjones243 looking at this PR I also noticed that the .npmignore file is not configured correctly. It is still using the legacy version. Please review the generator for the correct configuration.

Resolved.

[blackfalcon]

:tada: This PR is included in version 3.0.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: