meltano
Allow developers to explicitly declare "unsupported streams"
Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/108
Originally created by @aaronsteers on 2021-04-16 18:30:23
As came up in the office hours session this week, it would be helpful if developers could expose which API endpoints they explicitly have not covered yet in their implementation.
As Douwe mentioned in the video link, the Singer Spec does already support an "unsupported" flag for catalog metadata, and this could be applied if the developer wanted to expose to potential users (and also in SingerHub) which streams and covered by the tap and which streams are not covered.
This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.
The idea would be allowing developers to declare WIP streams and declare them as unsupported until they're implemented.
This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.