There's lots of times in the API (including throughout most of the analysis library) where API methods require use of QgsVectorLayer for inputs and outputs. They then only use the layer for a getFeatures call or for other basic getters like crs/extent/fields.
These should be updated to use the more versatile QgsFeatureSource and QgsFeatureSink interfaces.
m-kuhn
commented
6 years ago
There's lots of times in the API (including throughout most of the analysis library) where API methods require use of QgsVectorLayer for inputs and outputs. They then only use the layer for a getFeatures call or for other basic getters like crs/extent/fields.
These should be updated to use the more versatile QgsFeatureSource and QgsFeatureSink interfaces.