Mixing
What is the markdown syntax for .NET Core templating
I have a .NET Core template and wondering how I can hide partial content from markdown file based on the flags set?
As you may see below I tried what I do in CS project files but it didn't work.
README.md
# Steps
- createSolutionFile.ps1
<!--#if (CacheSqlServer)-->
- sql-cache.ps1
1. create database `DistributedCache`
2. create schema `cache`
3. run the script
<!--#endif-->
- user-secrets.ps1
<!--#if (EntityFramework)-->
- scaffold.ps1
- migrate.ps1
<!--#endif-->
- build.ps1
<!--#if (WindowsService)-->
- windows-service.ps1
<!--#endif-->
asp.net-core asp.net-core-mvc asp.net-core-2.0
asked Nov 22 '18 at 0:38
cilerlercilerler
4,80864167
add a comment |
I have a .NET Core template and wondering how I can hide partial content from markdown file based on the flags set?
As you may see below I tried what I do in CS project files but it didn't work.
README.md
# Steps
- createSolutionFile.ps1
<!--#if (CacheSqlServer)-->
- sql-cache.ps1
1. create database `DistributedCache`
2. create schema `cache`
3. run the script
<!--#endif-->
- user-secrets.ps1
<!--#if (EntityFramework)-->
- scaffold.ps1
- migrate.ps1
<!--#endif-->
- build.ps1
<!--#if (WindowsService)-->
- windows-service.ps1
<!--#endif-->
asp.net-core asp.net-core-mvc asp.net-core-2.0
asked Nov 22 '18 at 0:38
cilerlercilerler
4,80864167
add a comment |
I have a .NET Core template and wondering how I can hide partial content from markdown file based on the flags set?
As you may see below I tried what I do in CS project files but it didn't work.
README.md
# Steps
- createSolutionFile.ps1
<!--#if (CacheSqlServer)-->
- sql-cache.ps1
1. create database `DistributedCache`
2. create schema `cache`
3. run the script
<!--#endif-->
- user-secrets.ps1
<!--#if (EntityFramework)-->
- scaffold.ps1
- migrate.ps1
<!--#endif-->
- build.ps1
<!--#if (WindowsService)-->
- windows-service.ps1
<!--#endif-->
asp.net-core asp.net-core-mvc asp.net-core-2.0
asked Nov 22 '18 at 0:38
cilerlercilerler
4,80864167
I have a .NET Core template and wondering how I can hide partial content from markdown file based on the flags set?
As you may see below I tried what I do in CS project files but it didn't work.
README.md
# Steps
- createSolutionFile.ps1
<!--#if (CacheSqlServer)-->
- sql-cache.ps1
1. create database `DistributedCache`
2. create schema `cache`
3. run the script
<!--#endif-->
- user-secrets.ps1
<!--#if (EntityFramework)-->
- scaffold.ps1
- migrate.ps1
<!--#endif-->
- build.ps1
<!--#if (WindowsService)-->
- windows-service.ps1
<!--#endif-->
asp.net-core asp.net-core-mvc asp.net-core-2.0
asp.net-core asp.net-core-mvc asp.net-core-2.0
asked Nov 22 '18 at 0:38
cilerlercilerler
4,80864167
asked Nov 22 '18 at 0:38
cilerlercilerler
4,80864167
edited Nov 22 '18 at 14:52
cilerler
asked Nov 22 '18 at 0:38
cilerlercilerler
4,80864167
asked Nov 22 '18 at 0:38
cilerlercilerler
4,80864167
asked Nov 22 '18 at 0:38
cilerlercilerler
4,80864167
4,80864167
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The templating engine by default only supports these conditional operators only in a certain list of file types, sometimes with varying syntax. You can find that list of files in the source of the orchestrator. As of now, the list does not include Markdown files though, which is why you are not getting any functionality there.
Fortunately, there appears to be a way to configure special custom operations on custom file types inside the template.json, which allows you to define custom operations e.g. for conditional operators.
Adding something like this should work:
"SpecialCustomOperations": {
"**/*.md": {
"operations": [
{
"type": "conditional",
"configuration": {
"if": ["---#if"],
"else": ["---#else"],
"elseif": ["---#elseif", "---#elif"],
"endif": ["---#endif"],
"trim" : "true",
"wholeLine": "true",
}
}
]
}
}
It should allow you to use conditionals like this in your .md files:
# This is an example Markdown
---#if (FooBar)
Foo bar
---#elif (BarBaz)
Bar baz
---#else
Baz qux
---#endif
Note that I used a different syntax here as a single-line based syntax is a lot easier to configure.
answered Nov 22 '18 at 13:52
pokepoke
213k46331390
@cilerler Could you please not edit the whole answer like that? There is a reason I used a different syntax here. Non-line-based conditionals are more complicated to set up since you need actionable conditionals and additional actions. – If you want to maintain the syntax of conditionals from the question and you figure out a working configuration for that, you are free to post that as a separate answer.
– poke
Nov 22 '18 at 15:05
my bad, sorry. I didn't realize you did it on purpose. Thanks again...
– cilerler
Nov 22 '18 at 15:07
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%2f53422381%2fwhat-is-the-markdown-syntax-for-net-core-templating%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
The templating engine by default only supports these conditional operators only in a certain list of file types, sometimes with varying syntax. You can find that list of files in the source of the orchestrator. As of now, the list does not include Markdown files though, which is why you are not getting any functionality there.
Fortunately, there appears to be a way to configure special custom operations on custom file types inside the template.json, which allows you to define custom operations e.g. for conditional operators.
Adding something like this should work:
"SpecialCustomOperations": {
"**/*.md": {
"operations": [
{
"type": "conditional",
"configuration": {
"if": ["---#if"],
"else": ["---#else"],
"elseif": ["---#elseif", "---#elif"],
"endif": ["---#endif"],
"trim" : "true",
"wholeLine": "true",
}
}
]
}
}
It should allow you to use conditionals like this in your .md files:
# This is an example Markdown
---#if (FooBar)
Foo bar
---#elif (BarBaz)
Bar baz
---#else
Baz qux
---#endif
Note that I used a different syntax here as a single-line based syntax is a lot easier to configure.
answered Nov 22 '18 at 13:52
pokepoke
213k46331390
@cilerler Could you please not edit the whole answer like that? There is a reason I used a different syntax here. Non-line-based conditionals are more complicated to set up since you need actionable conditionals and additional actions. – If you want to maintain the syntax of conditionals from the question and you figure out a working configuration for that, you are free to post that as a separate answer.
– poke
Nov 22 '18 at 15:05
my bad, sorry. I didn't realize you did it on purpose. Thanks again...
– cilerler
Nov 22 '18 at 15:07
add a comment |
The templating engine by default only supports these conditional operators only in a certain list of file types, sometimes with varying syntax. You can find that list of files in the source of the orchestrator. As of now, the list does not include Markdown files though, which is why you are not getting any functionality there.
Fortunately, there appears to be a way to configure special custom operations on custom file types inside the template.json, which allows you to define custom operations e.g. for conditional operators.
Adding something like this should work:
"SpecialCustomOperations": {
"**/*.md": {
"operations": [
{
"type": "conditional",
"configuration": {
"if": ["---#if"],
"else": ["---#else"],
"elseif": ["---#elseif", "---#elif"],
"endif": ["---#endif"],
"trim" : "true",
"wholeLine": "true",
}
}
]
}
}
It should allow you to use conditionals like this in your .md files:
# This is an example Markdown
---#if (FooBar)
Foo bar
---#elif (BarBaz)
Bar baz
---#else
Baz qux
---#endif
Note that I used a different syntax here as a single-line based syntax is a lot easier to configure.
answered Nov 22 '18 at 13:52
pokepoke
213k46331390
@cilerler Could you please not edit the whole answer like that? There is a reason I used a different syntax here. Non-line-based conditionals are more complicated to set up since you need actionable conditionals and additional actions. – If you want to maintain the syntax of conditionals from the question and you figure out a working configuration for that, you are free to post that as a separate answer.
– poke
Nov 22 '18 at 15:05
my bad, sorry. I didn't realize you did it on purpose. Thanks again...
– cilerler
Nov 22 '18 at 15:07
add a comment |
The templating engine by default only supports these conditional operators only in a certain list of file types, sometimes with varying syntax. You can find that list of files in the source of the orchestrator. As of now, the list does not include Markdown files though, which is why you are not getting any functionality there.
Fortunately, there appears to be a way to configure special custom operations on custom file types inside the template.json, which allows you to define custom operations e.g. for conditional operators.
Adding something like this should work:
"SpecialCustomOperations": {
"**/*.md": {
"operations": [
{
"type": "conditional",
"configuration": {
"if": ["---#if"],
"else": ["---#else"],
"elseif": ["---#elseif", "---#elif"],
"endif": ["---#endif"],
"trim" : "true",
"wholeLine": "true",
}
}
]
}
}
It should allow you to use conditionals like this in your .md files:
# This is an example Markdown
---#if (FooBar)
Foo bar
---#elif (BarBaz)
Bar baz
---#else
Baz qux
---#endif
Note that I used a different syntax here as a single-line based syntax is a lot easier to configure.
answered Nov 22 '18 at 13:52
pokepoke
213k46331390
The templating engine by default only supports these conditional operators only in a certain list of file types, sometimes with varying syntax. You can find that list of files in the source of the orchestrator. As of now, the list does not include Markdown files though, which is why you are not getting any functionality there.
Fortunately, there appears to be a way to configure special custom operations on custom file types inside the template.json, which allows you to define custom operations e.g. for conditional operators.
Adding something like this should work:
"SpecialCustomOperations": {
"**/*.md": {
"operations": [
{
"type": "conditional",
"configuration": {
"if": ["---#if"],
"else": ["---#else"],
"elseif": ["---#elseif", "---#elif"],
"endif": ["---#endif"],
"trim" : "true",
"wholeLine": "true",
}
}
]
}
}
It should allow you to use conditionals like this in your .md files:
# This is an example Markdown
---#if (FooBar)
Foo bar
---#elif (BarBaz)
Bar baz
---#else
Baz qux
---#endif
Note that I used a different syntax here as a single-line based syntax is a lot easier to configure.
answered Nov 22 '18 at 13:52
pokepoke
213k46331390
edited Nov 22 '18 at 15:00
answered Nov 22 '18 at 13:52
pokepoke
213k46331390
answered Nov 22 '18 at 13:52
pokepoke
213k46331390
answered Nov 22 '18 at 13:52
pokepoke
213k46331390
213k46331390
@cilerler Could you please not edit the whole answer like that? There is a reason I used a different syntax here. Non-line-based conditionals are more complicated to set up since you need actionable conditionals and additional actions. – If you want to maintain the syntax of conditionals from the question and you figure out a working configuration for that, you are free to post that as a separate answer.
– poke
Nov 22 '18 at 15:05
my bad, sorry. I didn't realize you did it on purpose. Thanks again...
– cilerler
Nov 22 '18 at 15:07
add a comment |
@cilerler Could you please not edit the whole answer like that? There is a reason I used a different syntax here. Non-line-based conditionals are more complicated to set up since you need actionable conditionals and additional actions. – If you want to maintain the syntax of conditionals from the question and you figure out a working configuration for that, you are free to post that as a separate answer.
– poke
Nov 22 '18 at 15:05
my bad, sorry. I didn't realize you did it on purpose. Thanks again...
– cilerler
Nov 22 '18 at 15:07
@cilerler Could you please not edit the whole answer like that? There is a reason I used a different syntax here. Non-line-based conditionals are more complicated to set up since you need actionable conditionals and additional actions. – If you want to maintain the syntax of conditionals from the question and you figure out a working configuration for that, you are free to post that as a separate answer.
– poke
Nov 22 '18 at 15:05
@cilerler Could you please not edit the whole answer like that? There is a reason I used a different syntax here. Non-line-based conditionals are more complicated to set up since you need actionable conditionals and additional actions. – If you want to maintain the syntax of conditionals from the question and you figure out a working configuration for that, you are free to post that as a separate answer.
– poke
Nov 22 '18 at 15:05
my bad, sorry. I didn't realize you did it on purpose. Thanks again...
– cilerler
Nov 22 '18 at 15:07
my bad, sorry. I didn't realize you did it on purpose. Thanks again...
– cilerler
Nov 22 '18 at 15:07
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%2f53422381%2fwhat-is-the-markdown-syntax-for-net-core-templating%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
