We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When you sync a file that is nested in your src folder e.g.
src > Client-Code > UI > gui.lua
It creates:
"ReplicatedStorage": { "$className": "ReplicatedStorage", "Source": { "$path": "src" }, "Client-Code": { "UI": { "gui": { "$path": "src/Client-Code/UI/gui.lua" } } } }
It should auto fill in the class names as well like so:
"ReplicatedStorage": { "$className": "ReplicatedStorage", "Source": { "$path": "src" }, "Client-Code": { "$className": "Folder", "UI": { "$className": "Folder", "gui": { "$path": "src/Client-Code/UI/gui.lua" } } } }
Otherwise, you get this error: [ERROR rojo] Rojo project nodes must specify either $path or $className.
The text was updated successfully, but these errors were encountered:
This looks like a bug for the VS Code plugin repository!
I filed a bug for you over there, I'm going to go ahead and close this one: rojo-rbx/vscode-rojo#16
Sorry, something went wrong.
No branches or pull requests
When you sync a file that is nested in your src folder e.g.
src > Client-Code > UI > gui.lua
It creates:
It should auto fill in the class names as well like so:
Otherwise, you get this error:
[ERROR rojo] Rojo project nodes must specify either $path or $className.
The text was updated successfully, but these errors were encountered: