<@U06CBKL5W7L> I hope it's ok to ping you directly...
# plugins-general
l
@aaronsteers I hope it's ok to ping you directly. I'm working on the PR for
tap-github
to add the repo list, and I think I caught a bug in the sdk, but wanted to check with you if I'm using it correctly:
Copy code
tap1 = TapGitHub(config=REPO_LIST_CONFIG)
tap1.run_discovery()
catalog = tap1.catalog_dict
set_catalog_stream_selected(catalog, "issue_comments", selected=False)
# now I expect catalog to contain "selected": false for the issue_comments stream, but it doesn't
tap2 = TapGitHub(config=REPO_LIST_CONFIG, catalog=catalog)
tap2.sync_all()
# I would expect tap2 to NOT sync the issue_comments stream
set_catalog_stream_selected
seems to modify a copy of a part of the original catalog, and not the object passed, meaning it seems to have no effect. Is my code above correct (or is the bug in here)?
meh, I just saw #C01PKLU5D1R I should have posted there instead, sorry!
a
In general, yes, posting to #C01PKLU5D1R is preferred for general visibility, but yes, I see what you mean. One second though while I check something...
@laurent - yes, I believe this is fixed in the release coming out later today. https://gitlab.com/meltano/sdk/-/merge_requests/146
At least, I can see that this was refactored/rewritten.
All of the helpers modules prefixed with
_
are somewhat more raw and untested, hence the private module naming convention. In general, you should avoid calling those directly because they may be removed/refactored without warning. However, with @edgar_ramirez_mondragon's latest update, we agreed in that MR that we should start moving towards what the public and stable method signatures should be.
l
Nice! some of these helper functions are super helpful for testing taps. I was just looking at
deselect_all_streams
for instance. I think exposing some of them at least for that purpose would be nice.
a
Totally! Yes, we would like to. I used the same in one of my tests in the sample gitlab tap - which is a sign that it's needed and probably should be made non-private as soon as we can.
That said, the release that comes out today will break that existing method call, while introducing hopefully a better one.
If you want to add comments or suggestions on #209, that would be much appreciated.
l
ok, I guess I'll just hold back on that PR for a few hours then 馃檪