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
Injecting both src/renpy.json and src/renpyauto.json solves the issue, and Ren'Py static data can be correctly generated.
Not having this static data leads to the extension malfunctioning and some warnings being falsely triggered. The biggest example is the persistent variable has not been defaulted or defined when used in another file where they have been defaulted in. This is most likely the cause for #189.
The text was updated successfully, but these errors were encountered:
Ah thanks for that, we've been wondering why it didn't work in the stable version. We've been recommending people to just use the pre-release version up till now.
Nice catch, thanks! We can solve it by importing the JSON files as modules and adding "resolveJsonModule": true to tsconfig.json. As has been done in develop branch.
Hello,
Using
v2.0.15
on Code - OSS (installed from thecommunity/code
Archlinux repository):The extension has been added from within VSCode, from a simple marketplace search.
I have experiences the same "Initializing Ren'Py static data..." as issue #180, and when opening up dev console, the following message pops up:
The automatically installed extension contains the following files within the
luquedaniel.languague-renpy-2.0.15-universal
folder:Injecting both
src/renpy.json
andsrc/renpyauto.json
solves the issue, and Ren'Py static data can be correctly generated.Not having this static data leads to the extension malfunctioning and some warnings being falsely triggered. The biggest example is the
persistent variable has not been defaulted or defined
when used in another file where they have been defaulted in. This is most likely the cause for #189.The text was updated successfully, but these errors were encountered: