FEATURE - Support use of existing fragments and code for extension creation about open-ux-tools HOT 5 CLOSED

What modules need to be created or enhanced?
This is relevant for all extension types that include a fragment, i.e. custom page, custom section and custom column. But the same requirement is also valid for controller coding, thus the solution should be applied to custom actions as well. It must be a general pattern for all extension types. An existence check (mem-fs-editor.exists) shall take place for each fragment or controller file.

How would the functionality be exposed and how can it be consumed?
What we discussed are the two options: either have an additional input parameter for controlling the overwrite, or not to introduce such a parameter and generally check the file existence.
Design proposal is to take the second option: for each view or controller, check the existence first, and do not overwrite if the file is there.

@tobiasqueck @cfg74
Hope everybody agrees to this?

from open-ux-tools.

Fine, thanks. One additional remark, or special case: if the user passes the control content in the interface and specifies an existing control by name, the expectation probably is that the content get overwritten. I will program it like this.

from open-ux-tools.

@cfg74 Issue can be closed now

from open-ux-tools.

@cfg74 does #269 sufficiently cover your request?

from open-ux-tools.

Lgtm, thanks!

from open-ux-tools.