Kind reminder - would anyone from owners be willin...
# show-us-what-you-got
j
Kind reminder - would anyone from owners be willing to merge my PR? https://github.com/MeltanoLabs/tap-salesforce/pull/34 At least, I would appreciate if you merge the first commit, it speeds up the discovery a LOT. If you are not OK with the second commit, I can remove it and workaround it with overriding the metadata in maltano.yml.
d
Hey Jan, I don't see an issue with the first commit, but I would like to look more into the second one. That might impact people using the tap today.
If you could remove the second commit and Ideally add the new config property to the readme, I can approve
j
Done, please, approve.
May I kindly ask you for showing me a simple example how to override the metadata from the meltano.yml to do not need the commit I removed?
d
ok, all set on the MR. Not sure what you are asking in regard to the meltano.yml
j
Currently, anyType Salesforce properties are not transferred to targets. The second commit solves it. Other people here in the community suggest me to override the metadata for the Salesforce in meltano.yml to enforce the type of affected properties so they are loaded to targets.
In my case, e.g. LeadHistory.OldValue is of anyType. So my guess is that if I specify the following in the meltano.yml, it should work even without the second commit:
Copy code
extractors:
- name: tap-salesforce
  metadata:
    LeadHistory:
      OldValue:
        type: ["string", "null"]
Is my guess correct?
d
I haven't tried using this in meltano, so I'm not sure.
i
Hey all, I submitted a PR on this https://github.com/MeltanoLabs/tap-salesforce/pull/35 to fix the type hinting
j
Eh, sorry, I always forget to add this import, because I am using newest Python versions for a long time 😉