-
Notifications
You must be signed in to change notification settings - Fork 10
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
SearchField: Remove -field postfix from id #2365
base: search-field-updates
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 207031b 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 |
Size Change: -8 B (-0.01%) Total Size: 101 kB
ℹ️ View Unchanged
|
A new build was pushed to Chromatic! 🚀https://5e1bf4b385e3fb0020b7073c-theapxvwkr.chromatic.com/ Chromatic results:
|
GeraldRequired Reviewers
Don't want to be involved in this pull request? Comment |
npm Snapshot: Published🎉 Good news!! We've packaged up the latest commit from this PR (fae0595) and published all packages with changesets to npm. You can install the packages in webapp by running: ./services/static/dev/tools/deploy_wonder_blocks.js --tag="PR2365" Packages can also be installed manually by running: yarn add @khanacademy/wonder-blocks-<package-name>@PR2365 |
Checks look okay when I tried the npm snapshot in webapp! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
.changeset/cuddly-fireants-cheat.md
Outdated
@@ -0,0 +1,5 @@ | |||
--- | |||
"@khanacademy/wonder-blocks-search-field": minor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: This would probably account for a patch
change, but I also understand if you want to keep it as minor
as the API is being affected in some way (via the renderer HTML). Feel free to keep it or change it as you prefer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes thanks for catching that! I think patch
makes sense since the external api (props) hasn't changed
bed91f4
to
207031b
Compare
Summary:
Previously, the SearchField component was appending "-field" to the end of a provided id prop. We remove this post-fix and now use the
id
prop as isThis change is needed so when SearchField is used with LabeledField, LabeledField will set the id of the field element and wire it up with the label element. Since LabeledField works with a variety of components, the id shouldn't be modified by the field.
Issue: WB-1771
Test plan:
/?path=/story/packages-searchfield--default&args=id:test123
)