This is sort of an enhancement to the “Cascade Add” idea here
but the basic premise is this:
- If I update something in a parent task at the top of some design, I’d like that to cascade down subsequent tasks I select
For example, I have a fetch that has 5 total merge/transform etc., tasks after it and I change a field name from My_sweet_field to My_sweet_NEW_field, I’d like that change to cascade down to all 5 subsequent tasks *should I so choose*.
The same would be true for something like a data type, decimal selection, etc. Most of this is just asking for metadata to be refreshed when a change is made.
This is very key when importing files from S3. It’s a huge pain to change datatype selections because you have to remove the field entirely from every step, and then make your change and add it back.
Having changed you make (beyond just the addition of a new field) propagate would be a huge win.