"../../" Includes a bad practice?

[iamlamprey]

I'm migrating everything over to Rhapsody and currently just copy-pasting boilerplate changes between expansion subdirectories (i know). I'm at the stage where I'd ready to implement a real boilerplate solution, so:

is there anything inherantly wrong with including scripts from higher directories (or absolute paths)? Does anyone have any horror stories or cases where these scripts haven't compiled properly, specifically for Rhapsody, before I commit to this?

ie:

include("../../myBoilerplate.js");

// or 

include("C://users/me/Desktop/myBoilerplate.js");

Thanks in advance :)

[d.healey]

@iamlamprey said in "../../" Includes a bad practice?:

I'm migrating everything over to Rhapsody

DM me, the original Rhapsody boilerplate is not going to be updated, I have a new toolkit that is much better but it's not quite ready for release, but very nearly.

You should always place scripts in the Scripts folder.

For the Rhapsody boilerplate (and the new version) you should include it as a git submodule, then it's really easy to get the latest changes with a simple git pull