Regular expression matching in --filter
#2
Comments
nectar-gerrit
pushed a commit
that referenced
this issue
Jun 7, 2023
Problem #1 - They were using an unintialized variable for the new index values. This bug appears to have been in the initial codebase (6 years ago). I think this explains weird behavior I've noticed but been unable to pin down. Problem #2 - In the Publication case, we were not reindexing all of the numbered elements. This was the most likely cause of various reported and observed bogus validation errors in hidden fields, etc. Problem #3 - When the user Deletes an existing Publication or Grant, submits and the form is then redisplayed (because the Submit bounced) the deleted P or C is not hidden and therefore looks like it won't be undeleted. Change-Id: I3e35fe23e6c30c78938b0fc015471da3325e690a
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all,
As discussed in research cloud slack, I wondered what you think of the idea of permitting regex search when using the
--filteroption foropenstack allocation list?Use case: I want to filter by University of Melbourne email addresses. These will have a pattern of the form
.*[@.]unimelb\.edu\.au. Either a regex match, or a fuzzy match like--filter contact_email~=unimelb, would be awesome.~ Tim R.
The text was updated successfully, but these errors were encountered: