[Feature Request]: Review and made uniform the way a string's trim is applied where needed
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 19h
- Merged PRs (30d)
- 227
Description
### 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
Contributor guide
Research direction
Start by comparing how string trimming is handled in the DatabaseLookup, StringOperations, and TextFileOutput transform dialogs, then review the related issue #2806. Define the common trimming approach before tracing its use across the other transforms. Done means the applicable transforms use one consistent trimming behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100