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
In Hop, there are a lot of transforms where in their dialog gives the possibility to trim strings (es. DatabaseLookup, StringOperations, TextFileOutput, other ). Any transform uses a different approach to perform the string's trim. We would like to choose a new approach to perform string's trim (maybe by leveraging on Java String.trim function) and apply a refactoring to Hop code so that this same approach must be used everywhere needed
Hi,
I would like to add one more aspect. I have just run into the problem that the Trim option in the dialogues not only deletes spaces but also non-printable characters. I could only solve this by performing the trimming via the JavaScript function rtrim() in a separate transformation.
From my point of view, more precise documentation of which form of trim is used and, if possible, influencing the type of trimming makes sense.
What would you like to happen?
In Hop, there are a lot of transforms where in their dialog gives the possibility to trim strings (es. DatabaseLookup, StringOperations, TextFileOutput, other ). Any transform uses a different approach to perform the string's trim. We would like to choose a new approach to perform string's trim (maybe by leveraging on Java String.trim function) and apply a refactoring to Hop code so that this same approach must be used everywhere needed
This issue is also in relationship with #2806
Issue Priority
Priority: 3
Issue Component
Component: Transforms
The text was updated successfully, but these errors were encountered: