-
Notifications
You must be signed in to change notification settings - Fork 16
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
Several bug fixes and improvements of SmartNodeSelector
#178
Several bug fixes and improvements of SmartNodeSelector
#178
Conversation
986132d
to
6df3f16
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.
Nice! 🚀🐞🐛
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.
Tested and looks very nice! Some comments.
Seem to have issue with wildcard-functionality
Comments:
- OR operator only working on last node, gives issues otherwise.
- Export of data types: Should additional types be exported?
- Would be nice to test fixes in
VectorSelector
usage, but now a local pack ofwcc
and build ofwsc
does not work, aswsc
is not updated with regards to the fixes inSmartNodeSelector
- Having issues with wildcard operator "*". When using wildcard, the nodes does not seem to be selected.
} | ||
|
||
const prohibitedDelimiters = ["|"]; | ||
if (prohibitedDelimiters.includes(props.delimiter)) { |
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.
Should "|"
always be prohibited, or should it only be prohibited when OR
-operator is used - i.e. when useBetaFeatuers = true
?
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.
I see your point. The intention with a prohibited char was to guarantee consistent behaviour. No matter which allowed delimiter is assigned, one can always turn on or off the beta features without being confronted with sudden error messages. On the other hand, it is not quite appreciable yet how much the beta features are going to be used (or if they are going to be used at all). So there is the downside of restricting the component user (a bit). IMO, restricting the component user to not using one certain single char is not too much of a downside compared to the potential downside of an inconsistency (however, both downsides are rather minor). What do you think?
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.
I agree with your point. Both easier and safer to prioritize consistent behavior by always prohibit the OR
-operator, rather than wanting to use "|"
as a delimiter.
7d4fcef
to
449d0a9
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.
Really nice features and fixes! 👍
Tested and verified!
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.
Tested and found some issues.
Testing with usage in VectorSelector (local build) in webviz-subsurface plugin.
Note: VectorSelector
in wsc
must be updated with showAllSuggestions
prop
Issues:
- Scrolling in suggestions not working when Ctrl+space. If exiting the node edit and entering again, the scroll works.
- When Ctrl+space shows all suggestions, the
showAllSuggestions
setting remains active when re-entering node editing. I.e. when entering node, matching suggestions are shown in list. When Ctrl+space is entered all suggestions are shown. If one exit (push outside of the editing node in GUI) and enter the node edit again, all suggestions are still shown.
See also #188. |
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.
- Bug fix: Suggestions window not shown correctly when scrolling - Bug fix: Crash when switching between tabs in Webviz plugin - Feature: Ctrl+Space opens all suggestions - Bug fix: "-" was not allowed in node names
3635b38
to
ae21518
Compare
Also added no-suggestions-placeholder
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.
Tested and found issues:
- Ctrl+space stopped working?
- Remove debug code
react/src/lib/components/SmartNodeSelector/components/SmartNodeSelectorComponent.tsx
Outdated
Show resolved
Hide resolved
- Wildcards not supported in `findSuggestions` function - Mousedown on suggestion blurred input field -> unexpected behaviour - Added shaking timer property to securely remove it on unmount
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.
Tested functionality and reviewed code changes. Really nice features! 👍
Closes #149.
Closes #97.
Fixes #186.
Closes #188.
Addresses #128.