fix: correct naming in function for exporting css parts

[jason-capsule42]

Alaska Airlines Pull Request

Checklist:

• My update follows the CONTRIBUTING guidelines of this project
• 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

Summary by Sourcery

Fix the naming in the 'exposeCssParts' function to ensure correct CSS part exports and update the README.md with the latest auro-icon module version.

Bug Fixes:

• Correct the naming in the 'exposeCssParts' function to properly export CSS parts for styling.

Documentation:

• Update the README.md to reflect the new version of the auro-icon module.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR fixes an issue with CSS part naming in the auro-icon component by correcting the exportparts attribute value. It also includes an update to the bundled script version in the documentation.

Class diagram for AuroIcon component changes

classDiagram
    class AuroIcon {
        +exposeCssParts() void
    }
    note for AuroIcon "Updated exportparts attribute from 'iconSvg:svg' to 'svg:iconSvg'"

Loading

File-Level Changes

Change	Details	Files
Fixed CSS parts export naming in the component	Swapped the order of parts in exportparts attribute from 'iconSvg:svg' to 'svg:iconSvg' to correctly map the exposed part name This change ensures proper CSS part exposure for parent component styling	src/auro-icon.js
Updated component version reference in documentation	Bumped auro-icon version from 6.0.3 to 6.1.0 in the CDN script URL	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @jason-capsule42 - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[blackfalcon]

🎉 This PR is included in version 6.1.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀