Finally and absolutely clarify path techniques in Webstorm #2
Under the topic,
Configuring Folders Within a Content Root,
I found the following contextless statement:
"Files under a folder marked as Resource Root can be referenced relative to this folder. Excluded folders are not involved in indexing and therefore they are ignored while searching, parsing, watching etc."
So...
What is the context of 'can be referenced'?
Does this mean:
1. any file under any folder within the project folder can be referenced in any other file within the project folder? (webstorm can perform majic with paths on behalf of any referenced js library)
2. Sub-files (child folder files) within a folder designated in the 'Content Root Dialog' as a Content Root or a Resource Root can reference any other file that exists anywhere within the network of defined Content Root and Resource Root folders, even in dependent js libraries?
3. This only applies to 'source', 'static', and 'asset' files and is meaningless when trying to create references between and among source files and various js libraries?
If any of the above are correct or incorrect, does Webstorm offer a consistent and reliable method of handling any and all paths from the root of its project structure?
Thanks,
Kimball Johnson
Please sign in to leave a comment.
I'm not sure I understand your questions... Referencing here means path URLs used in your sources files - URLs in <script>, <link>, etc. tags in HTML, references in CSS, LESS, etc. Normally WebStorm tries to resolve these paths (to provide path completion/validation) relative either to current file or to the project root. But folders marked as resource root are treated as root folders by paths validator, so WebStorm will also try to resolve paths relative to this folder.
please can you clarify what libraries are meant? And what references you are talking about?
Elena,
As it turns out, the questions I have are answered in relation to open source deployment techniques and platforms.
Because I have spent the last few days researching and testing into this body of knowledge, I am able to understand Jetbrains design of Webstorm to a much greater degree.
And I see the validity of the comments in your response.
Thanks for the reply,
Kimball Johnson