Current Working
The Services view (and Service Types view) currently does not has a search feature. As registries grow, this will become a performance and UX problem. Search needs to be added.
Backwards-compatible approach
- Accept one optional query parameters on GET /services - search
- When search parameter is not provided, return all results or the full json(as the current response).
- When search parameters are present, return the response as the search result( if page parameter present then the new response else the old response).
- Return empty response if search result not found.
Input sanitization
- Strip and normalize whitespace
- Enforce search query length limits
- Validate against an allowlist of safe characters using regex(no special characters allowed, eg -
<,>, * and etc)
Current Working
The Services view (and Service Types view) currently does not has a search feature. As registries grow, this will become a performance and UX problem. Search needs to be added.
Backwards-compatible approach
Input sanitization
<,>,*and etc)