Skip to content
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

Rojo pathing issue with "." and "../path" #261

Closed
axia-roblox opened this issue Oct 28, 2019 · 1 comment
Closed

Rojo pathing issue with "." and "../path" #261

axia-roblox opened this issue Oct 28, 2019 · 1 comment
Labels
status: needs repro We need more information on how to reproduce this issue. type: bug Something happens that shouldn't happen version: 0.5

Comments

@axia-roblox
Copy link

When running rojo serve on a project.json file, rojo thinks a valid path doesn't exist (when in fact it does).

"ContainingFolder": {
    "$path": "."
},

"SomeValidPath": {
    "$path": "../SomeValidPath"
}

This seems to function as a workaround:

"ContainingFolder": {
    "$path": "../ContainingFolder"
},

"SomeValidPath": {
    "$path": "../SomeValidPath"
}
@LPGhatguy LPGhatguy added type: bug Something happens that shouldn't happen version: 0.5 status: needs repro We need more information on how to reproduce this issue. labels Nov 19, 2019
@LPGhatguy
Copy link
Contributor

Starting in Rojo 6.0, the first entry is no longer valid in Rojo due to project composition becoming a feature.

I wasn't able to reproduce the other case involving ... I don't think I understand the difference in the second path for the two examples. If you run into this issue again on newer versions of Rojo, feel free to create a new issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs repro We need more information on how to reproduce this issue. type: bug Something happens that shouldn't happen version: 0.5
Projects
None yet
Development

No branches or pull requests

2 participants