When something goes wrong or missing in a workspace it is really helpful that transformers show as being invalid by the cog becoming red, the input that is invalid is highlighted and it is then added to the invalid transformers list in the navigator. However, this is not the case for AttributeKeepers and AttributeRemovers, and it can sometimes be difficult to track down the source of where it went wrong in large workspaces. If these transformers can be treated the same way as other transformers it would save a lot of time!
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+1This would make debugging a lot easier! The AttributeManager however does this already (the cog becomes red when you try to remove an attribute that does not exist) and might prove to be a useful alternative.
+15- Safer
Updated idea statusGathering Interest→Archived
Idea merged into:
All the votes from this idea have been transferred.
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.