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

refactor(tabs): ensure valid tab id values #3530

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

mfranzke
Copy link
Member

@mfranzke mfranzke commented Nov 28, 2024

Proposed changes

We need to ensure that tabs only includes a valid tab value, whereas the current implementation might start with e.g. a number.

image

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (fix on existing components or architectural decisions)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Further comments

We need to ensure that tabs only includes a valid tab value, whereas the current implementation might start with e.g. a number.
@mfranzke mfranzke added the 🍄🆙improvement New feature or request label Nov 28, 2024
@mfranzke mfranzke self-assigned this Nov 28, 2024
@mfranzke mfranzke removed their assignment Nov 28, 2024
@mfranzke mfranzke enabled auto-merge (squash) November 28, 2024 18:52
@github-actions github-actions bot added the 🏘components Changes inside components folder label Nov 28, 2024
Copy link
Contributor

🔭🐙🐈 Test this branch here: https://db-ui.github.io/mono/review/refactor-tabs-resilience-for-tab-id-values

@mfranzke mfranzke changed the title refactor(tabs): resilience for tab ID values refactor(tabs): ensure valid tab ID values Nov 28, 2024
@mfranzke mfranzke changed the title refactor(tabs): ensure valid tab ID values refactor(tabs): ensure valid tab id values Nov 28, 2024
@nmerget
Copy link
Member

nmerget commented Nov 29, 2024

Shouldn't we do it for tab-panels as well?

@mfranzke
Copy link
Member Author

mfranzke commented Nov 29, 2024

Shouldn't we do it for tab-panels as well?

@nmerget Probably I'm misunderstanding your comment, but what are you referring to? The change is related to the tab panel even already, isn't it?: https://github.com/db-ui/mono/pull/3530/files#diff-3105bc16411a04c3e4f14f688a286a069e40378e9a57b2f526b678f93b1831dfR131

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏘components Changes inside components folder 🍄🆙improvement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants