-
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
[FX-4737] Do not pass enableResetSearch property #4089
Conversation
🦋 Changeset detectedLatest commit: 0ee49b5 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 |
Your alpha package is ready 🎉 |
@toptal-anvil ping reviewers |
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.
Is that normal that it passed CI checks, when enableResetSearch
prop is added?
23f0a97
to
0ee49b5
Compare
@rasitozcan I think there is a problem somewhere in types of |
FX-4737
Description
This pull request fixes the bug with passed
enableResetSearch
prop, introduced in #4075.Reason – spread operator is not type safe in this case (
packages/picasso/src/NativeSelect/NativeSelect.tsx
)No type check using spread operator (no error detected)
Normal typescheck when passing prop directly (error is detected)
How to test
yarn test namespaces/jobs/libs/jobs/src/containers/SendJobAwayModal/test.tsx
)Development checks
props
in component with documentationexamples
for componentPR 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?