SQLcl: MCP Server & SQL Prompt

i team,

This issue was observer on this version:

SQL> version
Oracle SQLDeveloper Command-Line (SQLcl) version: 26.1.2.0 build: 26.1.2.132.1334

Small but persistent friction point with SQLcl project export and APEXlang files:

When I export an application using either the APEX export API

select apex_export.zip (
                  p_source_files => apex_export.get_application (
                  p_application_id          => 116,
                  p_type                    => 'APEXLANG',
                  p_with_supporting_objects => 'N'
   )
                  );

or the SQLcl apex export command, generated APEXlang file and folder names preserve the normal readable casing, often camel case.

However, when the same application is exported through SQLcl project export, the file and folder names are forced to lowercase.

This is confusing and makes the exported project harder to work with. For example, a name like:

thisIsALongPropertyName

is much easier to read and search for than:

thisisalongpropertyname

It also creates unnecessary differences between export methods and may affect searching/navigation in editors, especially when trying to match an APEX component name to its generated file path.

Could SQLcl project export preserve the same casing used by the APEX export API / apex export command?

Is there any reason for lowercasing APEXLang filenames?