Fix bug where all workspaces are excluded in the Elwin interface when "Restrict allowed input files by name" is deselected #37430
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This bug was introduced by #37193 during this release.
This was discovered during testing for the new release from the BASIS instrument team.
Menu->Interfaces->Inelastic->Data Manipulation. Click the "Elwin" tab.
From the cog icon in the dialog, if you deselect "Restrict allowed input files by name" then no workspaces appear in the "Add Workspaces" dialog.
QStringList{""}
is actually creating a list with 1 item that is an empty string instead of creating an empty list. This causes the checkWorkspaceMultiSelector::hasValidSuffix
to always return false.Description of work
Summary of work
Fixes 5377: [Defect] Elwin file loading function not working properly in mantidworkbench nightly
Further detail of work
To test:
Menu->Interfaces->Inelastic->Data Manipulation. Click the "Elwin" tab.
Click "Add Workspaces" After valid workspaces are loaded and the "Restrict allowed input files by name" is unchecked, you should be able to see workspaces.
This does not require release notes because it was only introduced during this release.
Reviewer
Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.
Code Review
Functional Tests
Does everything look good? Mark the review as Approve. A member of
@mantidproject/gatekeepers
will take care of it.Gatekeeper
If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.