[Task]: harmonize the ActionMeta and TransformMeta classes
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
### What needs to happen?
even though Transforms and Actions are different objects in Apache Hop, they have a number of similarities that should be reflected in the code.
For example:
- there's a `TransformMeta.getTypeId()` that doesn't exist in `ActionMeta`
- there's a `ActionMeta.getTypeDesc()` that doesn't exist in `TransformMeta`
- `TransformMeta.getPluginId()` vs `ActionMeta.getAction().getPluginId()`
### Issue Priority
Priority: 3
### Issue Component
Component: Actions, Component: API, Component: Transforms
Contributor guide
Research direction
Start by comparing the ActionMeta and TransformMeta entry points named in the issue: getTypeId(), getTypeDesc(), getPluginId(), and getAction(). Determine which equivalent metadata methods should exist on both classes. Done means their similar capabilities are exposed consistently without changing the distinction between Actions and Transforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100