I’m currently rewriting one of my games, and I’ve run into a problem with autocomplete.
I have a framework that works like this. Imagine modulescript requires module m, and module m requires modulescript. Basically, they require eachother
The problem is that this completely breaks the autocomplete functionality, as shown in the video below.
repro RBXM
repro.rbxm (834 Bytes)
This issue is similar to the one discussed in another bug report.
To sum up, if you enter strict mode, the type checker is going to warn you about the cyclic module dependency, although there won’t be any runtime errors.
You can silence the warnings by casting type any with one of the requires, but that won’t affect autocompletion.
That’s actually really annoying how its not going to fixed.
Thanks for letting me know though. I’ll still leave this open in hopes that an engineer will change their mind, or i’ll open a feature request.
Thanks for the report! We’ll follow up when we have an update for you.
Closing this as we don’t plan to support type inference (which auto-complete uses) in module cycles.