There are currently two implementations of the FeatureSet within the Esri-verse that are incompatible. Making these two objects interoperable would allow greater ease of use in translating enterprise geodatabase feature classes and web-based feature layers.
For example, the gis.publish() accepts only one non-file input-- the feature collection. If the FeatureSet was compatible with the ArcPy implementation, a feature class could be turned into a FeatureSet and then a FeatureCollection for publishing. The current alternative is to either export the feature class into a hard file format, or create a map to host a service definition, and then publish.
https://developers.arcgis.com/python/api-reference/arcgis.gis.toc.html#arcgis.gis.Item.publish
This post makes the point very succinctly:
https://community.esri.com/t5/arcgis-api-for-python-questions/arcgis-featureset-arcpy-featureset/m-p/867723#M4501
So can we make the FeatureSet an actual FeatureSet?
