The quality of our adaptors varies significantly, because a) we tend to focus more of our time on certain adaptors (the ones we’re using right now) and b) some adaptors have only ever had one “minimal” release, or haven’t been maintained for a long time.
For those adaptors which aren’t in such good shape, I’d love to add some kind of flag to the the docs.
This would help set expectations when users come to look at docs for, say, cartodb (which at the time of writing has very out of date examples (which will be fixed soon)). It doesn’t mean “don’t use this adaptor”, but it means “take these docs with a pinch of salt”.
Reasons for applying this flag might be:
- The adaptor is literally unusable
- The adaptor uses an out of date/ older version of the target system (ie it’s literally out of date)
- The adaptor has insufficient documentation for users to be expected to use it
- The adaptor uses bad practice in the public API or docs - not just “not best practice” but actual antipatterns. Callbacks don’t count yet, but they might in six months time.
We might include a call for contributions to bring the adaptor up to date.