Built a tap this week for <Gong.io>, which will au...
# singer-tap-development
Built a tap this week for Gong.io, which will automatically transcribe calls and do some analytics on top of them. Their API is really just a couple endpoints, with the
endpoint having a bunch of nested tables, like "participants", "topics", "analytics", etc. As a developer, I could implement this mega-table as a single stream (truer to the interface and an "EL" workflow), or I could create more sensible child tables along the lines of the "multistream" approach described in this issue (https://gitlab.com/meltano/sdk/-/issues/167). I'm curious if anyone has a philosophical opinion on the approach?