This repository was archived by the owner on Oct 5, 2023. It is now read-only.
It now replaces __GUID()__ and __DATE()__ when it publishes a template#27
Open
robrich wants to merge 1 commit intoendjin:mainfrom
Open
It now replaces __GUID()__ and __DATE()__ when it publishes a template#27robrich wants to merge 1 commit intoendjin:mainfrom
robrich wants to merge 1 commit intoendjin:mainfrom
Conversation
You can also use formats e.g. __GUID(N)__ and __DATE(MM-dd-yyyy)__
TODO: The tests are NUnit style, not MSpec style, so probably need some cleanup
TODO: How could one specify this on creating a template? Do we want it to understand common Visual Studio rules like replacing <ProjectGuid>{0}</ProjectGuid> in a .csproj file or [assembly: Guid("{0}")]? This seems to make it more powerful for a subset of our users while making it less generic for others
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You can also use formats e.g. GUID(N) and DATE(MM-dd-yyyy)
TODO: The tests are NUnit style, not MSpec style, so probably need some cleanup
TODO: How could one specify this on creating a template? Do we want it to understand common Visual Studio rules like replacing {0} in a .csproj file or [assembly: Guid("{0}")]? This seems to make it more powerful for a subset of our users while making it less generic for others