feat(KeyValueInput): new component - #6639
Conversation
🦋 Changeset detectedLatest commit: 50bbae7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6639 +/- ##
==========================================
+ Coverage 91.06% 91.07% +0.01%
==========================================
Files 560 563 +3
Lines 10253 10336 +83
Branches 3692 3762 +70
==========================================
+ Hits 9337 9414 +77
- Misses 916 922 +6
... and 2 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
387c4e6 to
a3bd9fe
Compare
| /** | ||
| * KeyValuenput allow user to add key-value pairs | ||
| */ | ||
| export const KeyValueInput = ({ |
There was a problem hiding this comment.
Should we have a KeyValueInputField also ?
There was a problem hiding this comment.
We already have KeyValueField and I updated it in this PR to use KeyValueInput
1af6a22 to
63fe378
Compare
63fe378 to
3831a79
Compare
3831a79 to
2084cf1
Compare
2084cf1 to
16a8f10
Compare
16a8f10 to
50bbae7
Compare
Summary
Type
Summarize concisely:
The following changes were made:
KeyValueInput, inspired byKeyValueFieldKeyValueInputto defineKeyValueField(like other form components) instead of having a custom stand-alone componentselectvariant (instead of always being text)