Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-user transformations #286

Open
General-Fault opened this issue Sep 28, 2023 · 1 comment
Open

Per-user transformations #286

General-Fault opened this issue Sep 28, 2023 · 1 comment

Comments

@General-Fault
Copy link

It would be nice to be able to create transforms that are specific to a developer.
The idea would be to include a transform that typically would not be committed to source control and could be used by a developer to customize the transform output on their own machine.

I often make changes to app.Debug.config for developing and testing specific features of my application, or to transform the resulting configuration to include paths, certificate lookups, or other things that are specific to my development environment. On occasion, I will accidentally commit these changes to source control. I then have to revert those changes before they impact other developers. If there existed a mechanism to create a transform that ran after the configuration named transforms, I could keep my personal configuration changes out of the mix.

I suggest handling something like app.user.config or even app.machine.config that would be applied after app.Debug.config or app.Release.config. This concept could (and should) of course be extended to web configurations and other transforms.

@michaelmairegger
Copy link

Same issue here. Are there any news on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants