Irrelevant suggestions in autocomplete
Hi,
I've been noticing an increasing number of irrelevant suggestions in the autocomplete feature, and I recently encountered a situation that clearly illustrates the problem.
The attached example is from a TypeScript-based React (Next.js) web app project where I’m using the Mantine UI library—nothing unusual about the setup.
However, I’m puzzled by the irrelevant suggestions I receive for the width
property in my code, as shown in the recording. Despite the documentation being correctly referenced (I can easily navigate to the typedefs), the autocomplete provides zero useful suggestions.
For instance, I would expect target
and max-content
to appear among the top-ranked options, yet they’re completely absent.
This issue has been a growing frustration. One of the main reasons I switched to JetBrains products was their excellent navigation and autocomplete compared to other tools. Unfortunately, this hasn’t been meeting expectations lately.
I suspect the issue might be related to my settings, but none of the adjustments I’ve tried have resolved the problem.
Any insights or suggestions would be greatly appreciated!
Edit: edited for improved clarity.
请先登录再写评论。
Thanks for getting back to me, @Elena Pogorelova 🙏
I’ve edited my post above for better clarity, but I believe the GIF illustrates the issue quite well.
When I press
Ctrl+Space
with the cursor placed within the braces for thewidth
property, I’d expect the suggestions to be based on the type definitions for that property. However, I’m instead presented with options that seem irrelevant to the context.The
width
property accepts one of two specific strings (target
andmax-content
) or anumber
—nothing else. Yet, none of the suggestions reflect this.minimal repo project/file(s) and share this with us?