looking across several taps (`tap-csv`, `tap-s3`, ...
# singer-tap-development
looking across several taps (
) and there is quite a bit of duplication related to CSV parsing. i am considering making some improvements to
, but trying to avoid reinventing that part of the wheel. most taps seem to orient around parsing a file format, but some seem to be more oriented around the transfer mechanism for data files that could be in many different formats. s3, sftp, http are transfer protocols that could all have the same set of file formats that need to be parsed. how is the community thinking about this?