We should strip leading spaces in search queries

[anna-parker]

This is live on production, I cannot search by submissionId - can be tried by pasting the submissionId of any sequence into search:

e.g. https://main.loculus.org/seq/LOC_000PB42.1

[fhennig]

this one works: https://main.loculus.org/ebola-sudan/search?visibility_submissionId=true&submissionId=OQ673032.1

You can also find the one you've searched for if you drop the ".L"

[theosanderson]

This is because of a leading space in the search query when you copy-pasted (as @fhennig pointed out, you can see it in your URL) we should strip these

[chaoran-chen]

@theosanderson, do we want to strip leading spaces (1) from all search queries or (2) only from those where we perform a sub-string search? (2) seems quite safe to me, but I'm not sure about (1) – what if someone does have a leading space in their data?

[theosanderson]

Yes - good Q. I think my vote would be everything. Stripping is potentially dangerous but not stripping is also dangerous! (we might well not have set this field as substring). I think my vote would be strip everything and in 2 years when it catches someone out, implement configurability. But either would work for this case so I don't feel strongly - we could start with your idea.

[theosanderson]

Reposting from Slack: Actually the thing that gets copied is \r\n which is a newline sequence - that then gets converted to space when pasted into the search box - so probably room for improvement on the searchbox side too