How to use variable content in WebStorm file templates
I have this file template in WebStorm 2018.2:
#set($TestSuiteName = ${StringUtils.removeAndHump(${NAME}, "-")})
describe("#[[$TestSuiteName$]]#", () => {
it("should work", () =>
{
#[[$END$]]#
});
});
The important point of this question is the #[[$TestSuiteName$]]#
part of the template. What I want to achieve is, that $TestSuiteName
is replaced by the value calculated in the first template line and is selected for editing but can be accepted by pressing return.
All the template does right now is to print out "TestSuiteName" for the #[[$TestSuiteName$]]#
expression, which is not what I want. What it does right is to select the text "TestSuiteName" which it takes when I press return.
When I change the template to
#set($TestSuiteName = ${StringUtils.removeAndHump(${NAME}, "-")})
describe("$TestSuiteName", () => {
it("should work", () =>
{
#[[$END$]]#
});
});
then the filename is correctly camel-humped but it is not selected and the cursor jumps immediatly to the #[[$END$]]#
location.
What would be the correct way of getting the camel-humped filename selected for editing?
webstorm velocity
add a comment |
I have this file template in WebStorm 2018.2:
#set($TestSuiteName = ${StringUtils.removeAndHump(${NAME}, "-")})
describe("#[[$TestSuiteName$]]#", () => {
it("should work", () =>
{
#[[$END$]]#
});
});
The important point of this question is the #[[$TestSuiteName$]]#
part of the template. What I want to achieve is, that $TestSuiteName
is replaced by the value calculated in the first template line and is selected for editing but can be accepted by pressing return.
All the template does right now is to print out "TestSuiteName" for the #[[$TestSuiteName$]]#
expression, which is not what I want. What it does right is to select the text "TestSuiteName" which it takes when I press return.
When I change the template to
#set($TestSuiteName = ${StringUtils.removeAndHump(${NAME}, "-")})
describe("$TestSuiteName", () => {
it("should work", () =>
{
#[[$END$]]#
});
});
then the filename is correctly camel-humped but it is not selected and the cursor jumps immediatly to the #[[$END$]]#
location.
What would be the correct way of getting the camel-humped filename selected for editing?
webstorm velocity
add a comment |
I have this file template in WebStorm 2018.2:
#set($TestSuiteName = ${StringUtils.removeAndHump(${NAME}, "-")})
describe("#[[$TestSuiteName$]]#", () => {
it("should work", () =>
{
#[[$END$]]#
});
});
The important point of this question is the #[[$TestSuiteName$]]#
part of the template. What I want to achieve is, that $TestSuiteName
is replaced by the value calculated in the first template line and is selected for editing but can be accepted by pressing return.
All the template does right now is to print out "TestSuiteName" for the #[[$TestSuiteName$]]#
expression, which is not what I want. What it does right is to select the text "TestSuiteName" which it takes when I press return.
When I change the template to
#set($TestSuiteName = ${StringUtils.removeAndHump(${NAME}, "-")})
describe("$TestSuiteName", () => {
it("should work", () =>
{
#[[$END$]]#
});
});
then the filename is correctly camel-humped but it is not selected and the cursor jumps immediatly to the #[[$END$]]#
location.
What would be the correct way of getting the camel-humped filename selected for editing?
webstorm velocity
I have this file template in WebStorm 2018.2:
#set($TestSuiteName = ${StringUtils.removeAndHump(${NAME}, "-")})
describe("#[[$TestSuiteName$]]#", () => {
it("should work", () =>
{
#[[$END$]]#
});
});
The important point of this question is the #[[$TestSuiteName$]]#
part of the template. What I want to achieve is, that $TestSuiteName
is replaced by the value calculated in the first template line and is selected for editing but can be accepted by pressing return.
All the template does right now is to print out "TestSuiteName" for the #[[$TestSuiteName$]]#
expression, which is not what I want. What it does right is to select the text "TestSuiteName" which it takes when I press return.
When I change the template to
#set($TestSuiteName = ${StringUtils.removeAndHump(${NAME}, "-")})
describe("$TestSuiteName", () => {
it("should work", () =>
{
#[[$END$]]#
});
});
then the filename is correctly camel-humped but it is not selected and the cursor jumps immediatly to the #[[$END$]]#
location.
What would be the correct way of getting the camel-humped filename selected for editing?
webstorm velocity
webstorm velocity
asked Nov 18 '18 at 11:53
AndreasAndreas
6351926
6351926
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There is no way to do this currently:(
$VAR$
syntax has a special meaning in Webstorm templates - it's a kind of live template variable, a placeholder that allows placing cursor at certain position and editing a value when applying the template. To make such placeholders work, #[[$VAR$]]#
syntax is used to avoid conflicts with velocity variables (text in #[]#
is rendered as is - see http://velocity.apache.org/engine/1.7/user-guide.html#literals). That's why you get variable name instead of camel-humped file name when using #[[$TestSuiteName$]]#
.
We plan to provide a possibility to use the full power of live templates (live template functions, predefined variables, default values, etc.) in file templates. If you miss it, please vote for IDEA-161937, IDEA-173721 and linked tickets
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53360565%2fhow-to-use-variable-content-in-webstorm-file-templates%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is no way to do this currently:(
$VAR$
syntax has a special meaning in Webstorm templates - it's a kind of live template variable, a placeholder that allows placing cursor at certain position and editing a value when applying the template. To make such placeholders work, #[[$VAR$]]#
syntax is used to avoid conflicts with velocity variables (text in #[]#
is rendered as is - see http://velocity.apache.org/engine/1.7/user-guide.html#literals). That's why you get variable name instead of camel-humped file name when using #[[$TestSuiteName$]]#
.
We plan to provide a possibility to use the full power of live templates (live template functions, predefined variables, default values, etc.) in file templates. If you miss it, please vote for IDEA-161937, IDEA-173721 and linked tickets
add a comment |
There is no way to do this currently:(
$VAR$
syntax has a special meaning in Webstorm templates - it's a kind of live template variable, a placeholder that allows placing cursor at certain position and editing a value when applying the template. To make such placeholders work, #[[$VAR$]]#
syntax is used to avoid conflicts with velocity variables (text in #[]#
is rendered as is - see http://velocity.apache.org/engine/1.7/user-guide.html#literals). That's why you get variable name instead of camel-humped file name when using #[[$TestSuiteName$]]#
.
We plan to provide a possibility to use the full power of live templates (live template functions, predefined variables, default values, etc.) in file templates. If you miss it, please vote for IDEA-161937, IDEA-173721 and linked tickets
add a comment |
There is no way to do this currently:(
$VAR$
syntax has a special meaning in Webstorm templates - it's a kind of live template variable, a placeholder that allows placing cursor at certain position and editing a value when applying the template. To make such placeholders work, #[[$VAR$]]#
syntax is used to avoid conflicts with velocity variables (text in #[]#
is rendered as is - see http://velocity.apache.org/engine/1.7/user-guide.html#literals). That's why you get variable name instead of camel-humped file name when using #[[$TestSuiteName$]]#
.
We plan to provide a possibility to use the full power of live templates (live template functions, predefined variables, default values, etc.) in file templates. If you miss it, please vote for IDEA-161937, IDEA-173721 and linked tickets
There is no way to do this currently:(
$VAR$
syntax has a special meaning in Webstorm templates - it's a kind of live template variable, a placeholder that allows placing cursor at certain position and editing a value when applying the template. To make such placeholders work, #[[$VAR$]]#
syntax is used to avoid conflicts with velocity variables (text in #[]#
is rendered as is - see http://velocity.apache.org/engine/1.7/user-guide.html#literals). That's why you get variable name instead of camel-humped file name when using #[[$TestSuiteName$]]#
.
We plan to provide a possibility to use the full power of live templates (live template functions, predefined variables, default values, etc.) in file templates. If you miss it, please vote for IDEA-161937, IDEA-173721 and linked tickets
answered Nov 18 '18 at 13:54
lenalena
51.4k37380
51.4k37380
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53360565%2fhow-to-use-variable-content-in-webstorm-file-templates%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown