Transforms run even for Extractors with no Transformations defined
Before our update to remove the Load and Transform configuration steps from the UI, we had released an update (@derek-knox) that properly identified when a Tap had Transforms defined for it or not and switched the defaults for the Transform step to run
or skip
accordingly.
With the removal of the Transform configuration step, we have also removed that part of the code and we always run the Transform step.
That means that Transformations also run for Taps without ones (like tap-csv or, currently, the Google Ads one).
This is really minor cause we try to make available only Extractors with Transformations available, but we have discussions on bringing back the CSV extractor or even enable an Extractor for Postgres.
In those cases, it will be really confusing to show that we run Transforms without really running anything (dbt runs and then complains that there is nothing to do there). It also slows down considerably a very fast Extractor like the CSV one (which does not have to reach out of the server to a 3rd party API)
Also, I think that bringing this back should be pretty trivial cause we were already doing this check successfully, so there should be tested, ready to be used code in our repo's history.