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
I found a hacky solution by adjusting the tsconfig base paths, but as it is now, tgui-core imported components are running into the .yarn virtual caches instead of the actual definition of given components quite often if you try to follow their definition using language server functionality.
This also seems like it'll lead to inadvertent forking of repo-side components vs the tgui-core components.
The text was updated successfully, but these errors were encountered:
This is more of an issue caused by how we're installing modules in TG. Not only is it tucked away in a virtual folder, it's also the built/stripped down version.
Thus, it's not really this project's fault. Typically with UI libraries you would open the documentation directly rather than trying to decipher the (sometimes hellish) exports
I found a hacky solution by adjusting the tsconfig base paths, but as it is now, tgui-core imported components are running into the .yarn virtual caches instead of the actual definition of given components quite often if you try to follow their definition using language server functionality.
This also seems like it'll lead to inadvertent forking of repo-side components vs the tgui-core components.
The text was updated successfully, but these errors were encountered: