feat: New <k-stats-field> component
#7389
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bastianallgeier
force-pushed
the
feat/stats-field-component
branch
from
003046d to
8f5fd7c
Compare
bastianallgeier
force-pushed
the
feat/stats-field-component
branch
from
8f5fd7c to
52115bb
Compare
distantnative
approved these changes
Jul 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The new
<k-stats-field>component is basically rebuilding what happened in the<k-stats-section>but without the API props loading. We can plug it in as soon as the backend code for the field is also there (coming in the next PR)Changelog
✨ Enhancements
<k-stats-field>component<k-label>component now also acceptsfalsefor the input prop. This will switch the label element to an h2 and also remove the<abbr>for the invalid state. All fields that don't store any values will need this. We can also use it for the info field, which did still create its own headline.🐛 Bug fixes
h2that easily bleed into component rules.For review team