I have looked everywhere for documentation that explains the various template variables used in file watcher but I can't find anything. I know what some of them mean, but is there an exhaustive list of variables that are defined.
Examples:
$FilePathRelativeToProjectRoot$
$FileNameWithoutExtension$
$FileDirPathFromParent(js)$
Live Template Variables describe a couple but it doesn't seem to be an exhaustive list.
The only available documentation is the short macro description in the Macros dialog (shown on pressing Insert macro... button). BTW, this dialog has macro preview for currently opened file.
$FilePathRelativeToProjectRoot$ is a file path from project root/module content root folder. For example, if the file is <Project root>/app/stylesheets/style.less, $FilePathRelativeToProjectRoot$ will return app/stylesheets/style.less
$FileNameWithoutExtension$ is, well, a file name without extension:) A result of $FileName$.substring(0, file.lastIndexOf('.')). For style.less it will be style
$FileDirPathFromParent(js)$ - path to file directory relative to the js directory
Sorry folks, I knew I say it yesterday. You can see all the variables by selecting insert macro next to the File Watchers Arguments and Output paths fields.
Unfortunately some of them are indeed not documented, but they can be found on our tracker e.g. https://youtrack.jetbrains.com/issue/IDEA-28253
You can submit a feature request there to update online documentation to include those variables.
Actually the template variables is just a variable in any programming language, you can define whatever you want, evening a, b, ab ...... any legal
And the variable's scope is only in the template text, and you can define the variable like the default value in the "Edit Variables".
Related
Is it possible to replace the location property of the Parse Template? Instead of hardcoding in the location like so
Is it possible to replace this with a variable value that points to a path at runtime?
i have tried replacing the location with a variable but the project then fails to deploy because it cannot find that path. When the POST request comes in it states what file it wants parsed. Then we would ideally like to tell the parse template to go fetch that file but thus far i cant see anything that could help me online
Any suggestions would be very helpfull
I don't think it is possible to use an expression in the location attribute. Note that in the screenshot we can see that it is missing the Fx button to switch to expression mode, like the the Target Value attribute has.
As shown in the screenshot the current file has multiple instances of splice. However the Find in Path dialog does not find even those ones - let alone the many instances in other project files.
I also tried the Module and Scope : none find anything. However the Directory has the following:
So What is going on with the In Project, Module and Scope options?
Thanks to the suggestion by #Andrey this is now being tracked at https://youtrack.jetbrains.com/issue/IDEA-244685 .
Live templates -> edit variable.
I can specify groovy file in variable settings: groovyScript("C:/test.groovy")
Where is "home" directory to store my script? i Want something like that:
groovyScript("test.groovy")
For easy export config to another PC.
groovyScript's argument can be either the script text itself or a filename. In the latter case the filename is relative to idea or idea/bin directory. It's probably better to use absolute paths.
In recent IDEA builds you can share live templates by copying them to clipboard (Ctrl+C, see https://youtrack.jetbrains.com/issue/IDEA-141077)
I've a project that has a subproject (an XPC worker). Here I need to import one header from the main(parent) project. How do I do this?
I tried by setting(Sub project's) Header Search Path, User Header Search Path with values like $(SRCROOT) & $(SRCROOT)/../Interface.h. Also tried by changing the settings Recursive and Non-Recursive.
The way to solve these issues is to look at the actual compiler line when building the target to see what folders are being specified in the -I options and work from there. You need to go to the Build Log, find a file being compiled and then expand the command using the dropdown button thing on the right of the line.
The structure for all projects is fairly unique, so it's almost impossible to provide a one-size-fits-all fix for this.
I'd like to make a reference in my documentation to the source folder reference in Doxygen. These pages are already available in the index (the src folder file list, and one for each subfolder).
I've tried \ref and \link commands without any success (the ref is not resolved and the link aims to the current page).
One another (bad) solution should be to make an html link with the adress of the page (generatedDocumenation/html/dir_840ce71ebaba6062e222272fd2be405d.html for example), but I'm afraid this reference could change "randomly" at each generation, and it won't work for any kind of other output.
Do these pages have an implicit name to use for a ref command ?
Thanks in advance,
Babcool