-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
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
Services with $path but not $className turn into folders #331
Comments
I'm not sure if this one is a bug or something we should document. I'm going to make a couple assumptions about how your project is structured; let me know if I'm wrong here! Rojo always requires You should have a couple options to fix this:
|
You're exactly correct. Most of my partitions look like this: "ServerScriptService": {
"$className": "ServerScriptService",
"$path": "src/server"
}, So when $className is removed, it's assuming Folder. The reason this didn't happen with ReplicatedStorage is because every project node is nested within a subfolder, just as you mentioned. Definitely doesn't sound like a bug then, just something that could probably do with documentation |
After @nezuo's comment in #13, I'm wondering if this is something we should actually change instead of document. It's not likely that you want a Folder when you're in the same spot in the DOM as a service would be. We can probably loosen the logic here to overwrite |
I'm having the exact same issue, except this time Rojo crashes with
when trying to set $className to the correct service class name. EDIT: Rojo 6.0.2 on Windows 10 Insider Preview 21364.1 (co_release) |
This is fixed up in master! We have much better error messages, and now this case is handled as expected. |
I'm currently have the same issue. |
I have partitions to ReplicatedStorage, ServerScriptService, and StarterPlayerScripts. I removed the $className field from all three. When running
rojo build
, ReplicatedStorage syncs normally, however ServerScriptService and StarterPlayerScripts both create new Folders instead of placing instances in the actual service.The text was updated successfully, but these errors were encountered: