Autocomplete interaction callback request fails to parse localisations about discord-api-docs

[appellation]

We expect that autocomplete results should necessarily be locale-aware in order to provide meaningful results and therefore apps should be preferring to return results in the interaction locale anyway. Therefore we'll keep tracking this as a wishlist fix, but generally you should be able to use the workaround to cover this functionality. Is there a specific use-case that you're trying to solve for here?

[Jiralite]

I do not have a specific use case for wanting this behaviour other than for consistency. I just wanted to point out that the API specification and the documentation state these fields should work when they do not, hence the bug report.

Although not common, it does cause the odd one here and there to ask why their responses are not localised.

[advaith1]

I was surprised by #4721 classifying this as a bug - IMO this should just be considered the intended behavior and documentation should reflect that. If you already know what the locale is, then returning data in multiple locales just results in larger payloads for no reason.