-
Notifications
You must be signed in to change notification settings - Fork 15
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
[CPT-1479] Enable select clear button for the qb #4084
[CPT-1479] Enable select clear button for the qb #4084
Conversation
🦋 Changeset detectedLatest commit: 65b1162 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
@toptal-bot run package:alpha-release |
Greetings from FX team, @angelinastavniiciuc 👋 Thank you so much for contributing 🙇 We have got high priority ticket generated on our Kanban board so we will do our best to make your experience supreme! What's next? We will collaborate using this workflow. For you this practically means making sure DONE criteria is met and responding promptly to code review comments 😉 🙏 please, help us improve, rate your contributing experience after merge |
Your alpha package is ready 🎉 |
d9c4e10
to
87209b9
Compare
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.
Looks good, added suggestion in https://github.com/toptal/picasso/pull/4084/files#r1447127783
@toptal-anvil ping reviewers |
The behavior works correctly. Good job. However, do we have a ticket where we will introduce this in the documentation? I need help finding the property listed somewhere. |
@toptalwadiibasmi The property is provided from Picasso Select and it is listed there, |
Okey! I thought we would also have to update the field property documentation, but apparently, it wasn't typed in the documentation in the first place. I will approve as the code looks good and the test passes. |
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.
Looks good. Tested and works as expected.
QA tested, and almost everything works as expected 🥸 in exception to the following scenarios:
Also this scenario is not clear enough to me:
|
We synced with Rasit and established that it is not a reset functionality but actually clearing functionality so indeed the implementation did not match scenarios. So that answers to your first 2 questions When it comes to this
It's a typo. I was thinking too hard about selecting. 😂 The word should be cleared so |
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.
After some clarification, this is tested and good to go 🚀
b599552
to
65b1162
Compare
CPT-1479
Description
Describe the changes and motivations for the pull request.
How to test
Also plays
ruleenableReset
property is working as expectedScreenshots
Development checks
props
in component with documentationexamples
for componentBreaking change
PR commands
List of available commands:
@toptal-bot run package:alpha-release
- Release alpha version@toptal-anvil ping reviewers
- Ping FX team for reviewPR Review Guidelines
When to approve? ✅
You are OK with merging this PR and
nit:
to your comment. (ex.nit: I'd rename this variable from makeCircle to getCircle
)When to request changes? ❌
You are not OK with merging this PR because
When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:
How to handle the comments?