Testing development flow with adding a ~tilde search filter

This commit is contained in:
Viktor Lofgren 2023-10-24 15:35:15 +02:00
parent 72152f9d80
commit 8d1c3c754d
2 changed files with 5 additions and 0 deletions

View File

@ -14,6 +14,7 @@ public enum SearchProfile {
CORPO("corpo", SearchSetIdentifier.NONE),
YOLO("yolo", SearchSetIdentifier.NONE),
VINTAGE("vintage", SearchSetIdentifier.NONE),
TILDE("tilde", SearchSetIdentifier.NONE),
CORPO_CLEAN("corpo-clean", SearchSetIdentifier.NONE),
ACADEMIA("academia", SearchSetIdentifier.ACADEMIA),
PLAIN_TEXT("plain-text", SearchSetIdentifier.NONE),
@ -57,6 +58,9 @@ public enum SearchProfile {
subquery.searchTermsPriority.add("format:html123");
subquery.searchTermsPriority.add("js:false");
}
if (this == TILDE) {
subquery.searchTermsAdvice.add("special:tilde");
}
if (this == PLAIN_TEXT) {
subquery.searchTermsAdvice.add("format:plain");
}

View File

@ -15,6 +15,7 @@
</optgroup>
<optgroup label="Vintage">
<option {{#eq profile "vintage"}}selected{{/eq}} value="vintage">Web 1.0</option>
<option {{#eq profile "tilde"}}selected{{/eq}} value="tilde">~tilde/</option>
<option {{#eq profile "plain-text"}}selected{{/eq}} value="plain-text">Text Files</option>
</optgroup>
<optgroup label="Category">