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
Hi Gabriel!
Yes I can explain. All these tickets are technical debt that we want to cleanup.
A good example can be found in following PRs #2963, #2910 and there are many more examples.
We want to get rid of the getXml() and loadXml() methods in the Action classes and the TransformMeta classes.
for this we have a system with annotations @HopMetadataProperty() If we clean all of this we can in a later stage move to json or yaml representations of our pipelines and workflows.
Some extra things to take into account is when cleaning this up all arrays have to be moved to Lists.
The best way to get started on this is to start with an Action eg. #1992 as these usually do not have complex nested XML. Starting with a transform (especially those with many options and nested structures (file/field lists) can become quite complex.
If you start on these and ever get stuck feel free to create a draft PR and ask for some help.
What needs to happen?
Cleanup XML of transform String Operations
Issue Priority
Priority: 3
Issue Component
Component: Metadata
The text was updated successfully, but these errors were encountered: