Even with the split option from sqlcl, I still must sometimes use the Builder UI export because those are the only individual components that will install incrementally. I.e. when I need to deploy say a couple of dozen pages, but not all the pages in an application with more than a hundred pages, then I use component export wizard. To increase efficiency in that scenario, I put together a little greasemnkey/tampermonkey userscript: https://openuserjs.org/scripts/jrwarwick/Oracle_APEX_Component_Export_Enhancements
Maybe it is out of the scope of this plugin, but it would be great if a Pro-Polished version of the functionality I have in that userscript was included, and also the equivalent for other shared component types that often come in high volume (lists, tabs, etc).
Even with the split option from sqlcl, I still must sometimes use the Builder UI export because those are the only individual components that will install incrementally. I.e. when I need to deploy say a couple of dozen pages, but not all the pages in an application with more than a hundred pages, then I use component export wizard. To increase efficiency in that scenario, I put together a little greasemnkey/tampermonkey userscript: https://openuserjs.org/scripts/jrwarwick/Oracle_APEX_Component_Export_Enhancements
Maybe it is out of the scope of this plugin, but it would be great if a Pro-Polished version of the functionality I have in that userscript was included, and also the equivalent for other shared component types that often come in high volume (lists, tabs, etc).