Skip to content
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

Conversation

rubenthoms
Copy link
Collaborator

@rubenthoms rubenthoms commented Oct 13, 2021

  • Feature: OR operator in nodes (beta)
  • Bug fix: Placeholder not applied
  • Bug fix: Text width not calculated correctly initially
  • Feature: Case-insensitive search and apply (optional feature)
  • Feature: Export of data types
  • Feature: Search on descriptions
  • Bug fix: Clicking enter while node editing not finished jumped to next node (if available)
  • Improved and bug fixed: Arrow navigation within node input field
  • Feature: Tab navigation
  • Feature: End/Home navigation
  • Improved visual feedback
  • Ctrl+Space always opens all suggestions
  • Bug fix: Incorrect positioning when scrolling
  • Bug fix: Minus was not allowed in node names

Closes #149.
Closes #97.
Fixes #186.
Closes #188.
Addresses #128.

@rubenthoms rubenthoms self-assigned this Oct 13, 2021
@rubenthoms rubenthoms marked this pull request as ready for review October 14, 2021 11:10
@rubenthoms rubenthoms force-pushed the EQ_149-SmartNodeSelector-improvements-and-fixes branch from 986132d to 6df3f16 Compare October 18, 2021 11:18
Copy link
Collaborator

@anders-kiaer anders-kiaer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! 🚀🐞🐛

CHANGELOG.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@jorgenherje jorgenherje left a 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 of wcc and build of wsc does not work, as wsc is not updated with regards to the fixes in SmartNodeSelector
  • Having issues with wildcard operator "*". When using wildcard, the nodes does not seem to be selected.

}

const prohibitedDelimiters = ["|"];
if (prohibitedDelimiters.includes(props.delimiter)) {
Copy link
Collaborator

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?

Copy link
Collaborator Author

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?

Copy link
Collaborator

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.

Copy link
Collaborator

@jorgenherje jorgenherje left a 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!

@anders-kiaer anders-kiaer added the next release 🚢 To be included in next release label Nov 8, 2021
Copy link
Collaborator

@jorgenherje jorgenherje left a 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.

@tnatt tnatt mentioned this pull request Nov 8, 2021
2 tasks
@rubenthoms
Copy link
Collaborator Author

See also #188.

Copy link
Collaborator

@jorgenherje jorgenherje left a 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:

  • When entering node level, the filtered search removes non-matching suggestions, but then they reappear after a fraction of a second (without pushing Ctrl+space):
    MicrosoftTeams-image
  • The suggestions does not scroll to active/marked suggestion:
    image

- 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
@rubenthoms rubenthoms force-pushed the EQ_149-SmartNodeSelector-improvements-and-fixes branch from 3635b38 to ae21518 Compare November 9, 2021 13:49
Copy link
Collaborator

@jorgenherje jorgenherje left a 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

Copy link
Collaborator

@jorgenherje jorgenherje left a 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! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request next release 🚢 To be included in next release
Projects
Archived in project
3 participants