You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the tool only supports a fixed set of patterns. Even a trivial change would require making a fork of the tool, implementing the change in c#, recompile & redeploy.
We should improve this by making configuration more flexible, for example by using some marker replacement technique in user-given input.
For example:
one should be able to state that InformationalVersion should be:
"This is my fancy thingy {major}.{minor}, release {configuration}". Curly parts would be replaced with runtime values on each build.
The text was updated successfully, but these errors were encountered:
Currently the tool only supports a fixed set of patterns. Even a trivial change would require making a fork of the tool, implementing the change in c#, recompile & redeploy.
We should improve this by making configuration more flexible, for example by using some marker replacement technique in user-given input.
For example:
one should be able to state that InformationalVersion should be:
"This is my fancy thingy {major}.{minor}, release {configuration}". Curly parts would be replaced with runtime values on each build.
The text was updated successfully, but these errors were encountered: