-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Feat: Add displayTrigger boolean #1332
Conversation
@@ -443,17 +450,17 @@ CommandPalette.propTypes = { | |||
* first suggestion. Defaults to false. */ | |||
highlightFirstSuggestion: PropTypes.bool, | |||
|
|||
/** When suggestion is clicked, react-autosuggest needs to populate the input element | |||
/** When suggestion is clicked, react-autosuggest needs to populate the input element |
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.
not sure why these are appearing. They're not in my commit locally.
@mcrowder65 the snapshot tests are failing and we need some docs in the readme after this can be merged. Out of curiosity why not use something like the following?
my suggestion for the README.md
|
@asabaylus why not allow |
Good point, did you want to update the PR or shall I? |
@asabaylus addressed! |
@mcrowder65, there are several failing tests. The pallet needs to render unless
We still need a unit test. |
Codecov ReportBase: 100.00% // Head: 100.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #1332 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 7 7
Lines 218 221 +3
Branches 35 36 +1
=========================================
+ Hits 218 221 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Add
null
option toprops.trigger
, so that the trigger won't render. ex: