The portal should ensure that search phrases are above a minimum length (say 2 chars) to help prevent accidental running of single character searches (which are extremely expensive and may not complete before the browser times out).
assigned to @btasker
mentioned in issue #16
mentioned in commit 5e7326cb324529c25d0e9e3882f55e13046e3abd
Commit: 5e7326cb324529c25d0e9e3882f55e13046e3abd Author: B Tasker Date: 2023-12-30T18:15:17.000+00:00
feat: implement minimum search phrase length (utilities/file_location_listing#19)
There's a pretty basic implementation in place now - the portal will pop an alert if the phrase is < 3 chars.
It's pretty rudimentary
It's all I really need though - the aim is simply to avoid accidentally submitting a search for a single character.
It's also only enforced client side - at some point, I may have cause to have something else run searches via API
Activity
30-Dec-23 15:44
assigned to @btasker
30-Dec-23 15:45
mentioned in issue #16
30-Dec-23 18:15
mentioned in commit 5e7326cb324529c25d0e9e3882f55e13046e3abd
Commit: 5e7326cb324529c25d0e9e3882f55e13046e3abd Author: B Tasker Date: 2023-12-30T18:15:17.000+00:00Message
feat: implement minimum search phrase length (utilities/file_location_listing#19)
30-Dec-23 18:17
There's a pretty basic implementation in place now - the portal will pop an alert if the phrase is < 3 chars.
It's pretty rudimentary
It's all I really need though - the aim is simply to avoid accidentally submitting a search for a single character.
It's also only enforced client side - at some point, I may have cause to have something else run searches via API