You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Luau LSP v1.36, the luau-lsp.require.directoryAliases configuration was deprecated in favor of using aliases defined in the .luaurc file. Lune should be updated to respect this new configuration method.
However, transitioning to .luaurc poses a challenge since users who are still on earlier versions of Luau LSP will lose autocomplete functionality if we implement this change. A potential solutions would involve us determining the version of Luau LSP that is currently in use, or introducing a flag which allows users to explicitly specify if they want editor settings instead of a .luaurc change.
The text was updated successfully, but these errors were encountered:
However, transitioning to .luaurc poses a challenge since users who are still on earlier versions of Luau LSP will lose autocomplete functionality if we implement this change. A potential solutions would involve us determining the version of Luau LSP that is currently in use, or introducing a flag which allows users to explicitly specify if they want editor settings instead of a .luaurc change.
This seems like a non-issue to me, we should be fine to just make the change to use .luaurc without adding additional complexity to the command. People using Luau LSP most likely use an editor that auto-updates extensions (VSCode), so if they're on an older version it's because they have already messed with their editor config to disable auto update.
In Luau LSP v1.36, the
luau-lsp.require.directoryAliases
configuration was deprecated in favor of using aliases defined in the.luaurc
file. Lune should be updated to respect this new configuration method.However, transitioning to
.luaurc
poses a challenge since users who are still on earlier versions of Luau LSP will lose autocomplete functionality if we implement this change. A potential solutions would involve us determining the version of Luau LSP that is currently in use, or introducing a flag which allows users to explicitly specify if they want editor settings instead of a.luaurc
change.The text was updated successfully, but these errors were encountered: