Skip to content
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

feat(Accordion, Alert, Dialog, Form Error List, Heading)!: Require explicit heading levels #1819

Merged
merged 16 commits into from
Jan 22, 2025

Conversation

VincentSmedinga
Copy link
Contributor

Describe the pull request

What

Requires providing a level for Heading and a headingLevel for Accordion, Alert, Dialog, and Form Error List.

Why

The heading level has no sensible default; it can appear anywhere in the document’s hierarchy. We need people to consider which level fits best in each situation.

How

  • Made the appropriate props required
  • Updated tests and stories

Checklist

Before submitting your pull request, please ensure you have done the following. Check each checkmark if you have done so or if it wasn't necessary:

  • Add or update unit tests
  • Add or update documentation
  • Add or update stories
  • Add or update exports in index.* files
  • Start the PR title with a Conventional Commit prefix, as explained here.

Additional notes

n/a

@VincentSmedinga VincentSmedinga force-pushed the feat/require-heading-level branch from c5e18dd to 72cb92c Compare January 16, 2025 15:18
@github-actions github-actions bot temporarily deployed to demo-require-heading-level January 16, 2025 15:19 Destroyed
@VincentSmedinga VincentSmedinga marked this pull request as ready for review January 16, 2025 15:21
@VincentSmedinga VincentSmedinga requested a review from a team as a code owner January 16, 2025 15:21
@github-actions github-actions bot temporarily deployed to demo-require-heading-level January 21, 2025 12:23 Destroyed
@VincentSmedinga VincentSmedinga changed the title feat!: Require explicit heading levels feat(Accordion, Alert, Dialog, Form Error List, Heading)!: Require explicit heading levels Jan 21, 2025
@github-actions github-actions bot temporarily deployed to demo-require-heading-level January 22, 2025 10:35 Destroyed
@github-actions github-actions bot temporarily deployed to demo-require-heading-level January 22, 2025 10:50 Destroyed
@github-actions github-actions bot temporarily deployed to demo-require-heading-level January 22, 2025 11:40 Destroyed
@github-actions github-actions bot temporarily deployed to demo-require-heading-level January 22, 2025 11:42 Destroyed
Co-authored-by: Aram <37216945+alimpens@users.noreply.github.com>
@github-actions github-actions bot temporarily deployed to demo-require-heading-level January 22, 2025 13:03 Destroyed
alimpens
alimpens previously approved these changes Jan 22, 2025
@github-actions github-actions bot temporarily deployed to demo-require-heading-level January 22, 2025 14:06 Destroyed
@VincentSmedinga VincentSmedinga merged commit ef849ed into develop Jan 22, 2025
6 checks passed
@VincentSmedinga VincentSmedinga deleted the feat/require-heading-level branch January 22, 2025 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants