Cspace 4547 #4
Merged
Cspace 4547 #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…aping of unescaped backslashes and percent signs.
…ng unescaped chars; added Javadoc comments.
…opy and paste typo anyway) from the set of chars to escape in the services advanced search string. This is redundant as well, as backslashes appear to be preserved in the submitted search string.
…signs in what appears to be keyword search strings, reversing commit 4515107.
…maven-archiver/pom.properties.
…/target/maven-archiver/pom.properties." This reverts commit 21e7d21.
ghost
assigned
aronr
added a commit
that referenced
this pull request
Mar 7, 2012
CSPACE-4547: Allow the use of unescaped double quote marks and percent signs in advanced search fields.
remillet
pushed a commit
that referenced
this pull request
Apr 15, 2015
Update mmi acquisitions as per data map
jessemartinez
pushed a commit
to jessemartinez/application
that referenced
this pull request
Oct 24, 2018
Remove Breckenridge tenant
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow the use of unescaped double quote marks and percent signs in advanced search fields.
(Most other backslash-escaped characters should also work, with one exception: we don't yet support escaping of, and hence searching on, literal asterisks; these are still exclusively a wildcard character in advanced search.)