We were looking at a 3GB+ key_value table on a client project and were able to track it down to key_value, specifically entity_autocomplete settings.
By looking at them, we saw search paths in them, which pointed us to the select2 facets integration.
Each unique autocomplete settings array is persisted forever because it's passed to the autocomplete route with a key to the stored settings.
It must not contain dynamic elements. Why is this needed?
Active
2.0
Facets integration
Ok, I see, it's a facet, so it needs the context.
✨ Allow options to be passed to autocomplete element URLs Needs work would help with an alternative solution that would allow to pass a separate query string to autocomplete with the path, since this is not something that needs to be protected through the hash.