Fabián Castillo
Fabián Castillo
There's currently no way to do it in the UI. It's a good idea, I think we can definetely integrate into the project if someone wants to help with it....
Oh actually, I just checked the Flogo CLI and it doesn't have a command for uninstalling a contribution (activity, trigger, etc). The Flogo Web UI wraps the Flogo CLI, so...
This is similar to https://github.com/project-flogo/flogo-web/issues/1151 and the reason for both is that currently the UI can only handle contributions with a `descriptor.json` and cannot handle other types of imports. There...
Flogo Web only uses the information available in the descriptor json @fm-tibco any thoughts on this?
Okay yeah, that's another option
Is the `github.com/project-flogo/core/app/propertyresolver` added to the `imports` section? Can you please add an example of the usage (an app.json)? I'm not familiar yet with propertyresolver usage.
The UI assumes that Flogo allows the use of mappings in the activity settings. It seems that's not case and the UI should prevent the "mapping" wrapper from happening. So...
As noted in Gitter, there are exceptions to the mappings in settings. The "return" type activities do support the mappings in settings so the UI should still support using those...
Even though the trigger instances are not deleted the unused triggers are not serialized when exporting/building the app so it should not be an issue for exported apps. The thing...
Thanks for the detailed explanation. We were already thinking about enhancing the trigger selection window, here's what we currently have in mind: