This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Alternative for Environment TagHeper domain #5671
Comments
The But something like this can certainly be done: <environment names="Development">
<true>
…
</true>
<false>
…
</false>
</environment> |
(Not saying it's worth it or that it's a good idea, but it's implementable.) |
Another alternative to consider would be something like: <environment names="Development">
…
</environment>
<environment names="Development" behavior="OppositeDay">
…
</environment> Or at least something like that. |
Another option to consider: Another alternative to consider would be something like: <environment names="Development">
…
</environment>
<environment excludeNames="Development">
…
</environment> And you can't set both @DamianEdwards thoughts on this? I think this could clean up the default templates. And, of course, Hubbup. |
maybe: <environment include="Development">
...
</environment>
<environment exclude="Development">
...
</environment> And keep support for names as it is now. |
Yeah I dig this. @danroth27 totally digs this too. |
Let's go with @DamianEdwards 's suggestion in #5671 (comment). |
@Eilon @DamianEdwards or maybe options are may
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From @vkichline on October 8, 2015 22:32
I see this pattern in the Web Application template's _ValidationScriptsPartial.cshtml:
This pattern above seems brittle; if I add a new environment setting, I have a lot of searching and modification to do.
I wish I had something like:
…or:
Copied from original issue: aspnet/Razor#567
The text was updated successfully, but these errors were encountered: