mbed export -h missing description of parameter (-n)

[maclobdell]

The help for export does not list -n which is extremely useful because it allows the user to define a specific name for the exported project - otherwise it comes out as "Unnamed_Project".

Actually, I think that specifically naming the project should be required.

C:\xxx>mbed-cli --version 0.8.5

C:\xxx>mbed export -h usage: mbed export [-h] -i IDE [-m MCU] [--source SOURCE] [-c] [-S] [-v] [-vv]

Generate IDE project files for the current program.

optional arguments: -h, --help show this help message and exit -i IDE, --ide IDE IDE to create project files for. Example: UVISION4, UVISION5, GCC_ARM, IAR, COIDE -m MCU, --mcu MCU Export for target MCU. Example: K64F, NUCLEO_F401RE, NRF51822... --source SOURCE Source directory. Default: . (current dir) -c, --clean Clean the build directory before compiling -S, --supported Shows supported matrix of targets and toolchains -v, --verbose Verbose diagnostic output -vv, --very_verbose Very verbose diagnostic output

C:\xxx>mbed export -m NCS36510 -i uvision -n blinky

Successful exports:

• NCS36510::uvision C:\xxxx\mbed-os\core.build\export\blinky_uvision_NCS36510.zip

[screamerbg]

The flag won't be introduced because -n was temporarily changed in project.py. Now the default behavior is restored. @sg- @0xc0170

[0xc0170]

The flag won't be introduced because -n was temporarily changed in project.py. Now the default behavior is restored.

What's the default behavior ? What's the project name when exporting? I don't remember -n being changed. I could not locate anything in the git log, please provide a reference

[maclobdell]

@screamerbg @0xc0170 At this time, exporting a project results in Unnamed_Project... Highly recommend that the exported project assumes the name of the application or test that is in the directory that the export call is made from.