When I noticed the lag, that told me that the cut tool didn't work. I cannot recall if I tried my "bug fix" with a feature layer. Maybe it works?
Blame Kelly for opening my eyes to feature collections. They are amazingly useful!
Agreed, feature layers from feature collections are a great thing but they are limiting when your app requires editing and/or advanced querying capabilities.
Is there information in the documentation about what makes feature layers from feature collections so great?
You get a feature layer w/o having to publish an arcgis server map or feature service. That may or may not appeal to you...the main sample in the SDK that does this takes data from a 3rd party (flickr) and creates a feature layer from it: https://developers.arcgis.com/en/javascript/jssamples/fl_featureCollection.html
For the ESRI samples, right now it takes about 2-3 seconds for the cut process to complete. It takes about a second to start displaying any change.
- how long are you waiting for the cut operation to complete?
I'm guessing this is in reference to my personal project. No. I use my own GeometryService from my own ArcGIS Server.
- do you see a request to the cut endpoint on tasks.arcgisonline.com?
The sample, no. Proxy within my personal project for layers, yes. Even the GeometryService is proxied. Interestingly, all of my cut requests are instantaneous. No lag.
- do you have a proxy set up when running this sample locally?
Thanks. Since the sample in question doesn't include cut, you need to modify it and run it locally. When you do this, you have to have a proxy configured on the web server where you run the sample if you want to successfully use services on tasks.arcgisonline.com and sampleserver3.
I don't know where this leaves us...there are a number of moving parts here but I'll try to summarize:
- the editor with cutVisible: true works as designed but requires a proxy on the web server where your app runs
- the editor's cut tool is not supported with feature layers from feature collections and we'll do a better job of indicating this in the docs as well via a message logged to the browser's console when you try to do this