Adds a abort button to editor form if autosave and autoform is true #1512
Conversation
johnnyblasta
changed the title
There was a problem hiding this comment.
I have tested with related tables and it works when both autoSave and autoForm is true. As the abort function is only added to the main feature it is not necessary to do anything special for related tables. It won't be possible to abort a child layer creation in this way, but I don't think that it is necessary to support that. It will only confuse the users (and developers). Aborting the main feature will also delete any newly created child features, so that is also OK.
On the other hand, when autoSave is false it crashes on abort if the feature has related layers configured. I'm not sure that it is this PR that is the culprit, it may be an earlier undiscovered bug in related tables. It think the crash occurs because when deleteFeature tries to delete a feature that has not been auto saved, it first tries to read related related objects using the temporary fid as CQL. If the FK-field in the child is an integer, the server won't be able to parse the temporary fid (which is a guid) and crashes instead of returning an empty set. The remedy would be to add a check in deleteFeature to check if the feature is saved to server before trying to delete its children.
Closes #1508