-
Notifications
You must be signed in to change notification settings - Fork 185
feat: Permit mapper plugins as valid blocks #9105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for meltano ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
@edgarrmondragon Should we just remove the portion of the failing |
We probably just need to remove that test. |
…o mappings is invoked by the plugin name
… name is invoked by the ambiguous plugin/mapping name
I removed the part of the test in 96fd5a4. I updated a separate part in d4047a9 to assert an |
I think this is definitely easier, so I'm OK with taking that path. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9105 +/- ##
=======================================
Coverage 95.47% 95.47%
=======================================
Files 259 259
Lines 21374 21388 +14
Branches 1291 1293 +2
=======================================
+ Hits 20406 20420 +14
Misses 775 775
Partials 193 193 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Trying to think what unexpected behavior this might cause for users, but can't think of any 🤔 |
There is no check for conflicts between mapper plugin name and mapping name. I don't actually know which one it is resolving here:
This is what I was talking about above:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The mapper-level config
doesn't seem to be used and instead the last found mapping's is used 🤔
Description
Removes the
block violates set requirements: Expected unique mappings name not the mapper plugin name:
error message to optimistically allow mappers to be invoked directly, without having to instead reference a mapping.
As far as I see it, a mapping is just aliased config for mapper plugins. Some mappers will only ever need to perform a single function, so it doesn't makes sense to define a mapping in that case - you may as well just invoke the mapper directly; which is what this PR is addressing. For
meltano-map-transformer
and similar, I believe there is still value in mappings as it prevents you having toinherit_from
a basemeltano-map-transformer
to define your reusable mappings (although I think they are functionally the same) - i.e.and
Related Issues