fix: update whitespace & line endings in doc

[chrisfalaska]

Alaska Airlines Pull Request

Summary

After running npm run build doc file generated modifications based on whitespace & line ending adjustments.

Committing changes to select component auto-generated doc file.

Bug Fixes:

• Ensure documentation is checked in after the build process to prevent discrepancies between the code and its documentation.

Documentation:

• Update the documentation for the auro-select component to ensure consistency and accuracy in the demo examples.

Summary by Sourcery

Fix the process to check in documentation after the build to maintain consistency between code and documentation, and update the auro-select component documentation for accuracy.

Bug Fixes:

• Ensure documentation is checked in after the build process to prevent discrepancies between the code and its documentation.

Documentation:

• Update the documentation for the auro-select component to ensure consistency and accuracy in the demo examples.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR addresses documentation consistency by committing auto-generated documentation changes after running npm run build. The changes primarily involve whitespace and line ending adjustments in the select component's demo documentation file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Normalize line endings and whitespace in auto-generated documentation	Adjust line endings from CRLF to LF Remove extra blank lines between content sections Standardize indentation in code examples	components/select/demo/index.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.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

chrisfalaska seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sourcery-ai]

Hey @chrisfalaska - 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.}

[rmenner]

🎉 This PR is included in version 1.6.0-beta.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀