I have a workspace and I want to turn it into a CutsomTransformer - as part of that process I want to rename a bunch of attributes to include a prefix (e.g., from a JSONFlattener) - This is mostly for readability.
For example I have several attributes which are coming from a JSONFlattner - in the original I never added a prefix, however, now I want to prefix with something like “layer.” - so something like “extent” would become “layer.extent”.
The issues is that when I add that prefix in then all the downstream transformers which use the properties break. Obviously going through and changing them would have taken me less time than writing this question but it’s certainly not the first time I’ve had this kind of issue.
In similar situations in the past I’ve been lazy and have simply renamed the new attribute to the old value.
There are quite a few situations where I think having this kind of functionality would do a lot to improve workspaces readability with little effort on the authors part. For example often when building a workspace it’s pretty common to just reuse the out-out-the box default attribute names (e.g., _area). Then once you’ve finished the bulk of the work maybe you see that it’s unclear what “_area” actually is so you want to rename it - only to find our you’ve used it in several places. Perhaps you decide you can’t be bothered to rename it.
Has anyone run into this issue as well? How did you solve it (if at all)?
P.S - I added an idea:
