The limitation to just *.config makes sense, but I'd think it would be helpful to allow *.* for anything in the config folder. For some client-side work I'm doing in the backoffice, I put some xml files in the config folder I'd like to be editable by Config Tree.
You could fork the source to make it work with any file extension? I wouldn't want to do this for the main package, as really the focus is on *.config files.
Edit anything in config folder
The limitation to just *.config makes sense, but I'd think it would be helpful to allow *.* for anything in the config folder. For some client-side work I'm doing in the backoffice, I put some xml files in the config folder I'd like to be editable by Config Tree.
Hi Jon,
You could fork the source to make it work with any file extension? I wouldn't want to do this for the main package, as really the focus is on
*.config
files.The source is up on GitHub: https://github.com/leekelleher/umbraco-config-tree
The only change should be made here ... then hit the
build.cmd
in the root of the project and a package file should be made for you.I'm open to any ideas - so if you can think of a better way (that will benefit everyone), I'm all ears :-)
Good luck!
Cheers,
- Lee
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.