When a command bundle contains both config.py and a main script file with a prefix that sorts afterwards alphabetically, such as test_script.py, the parser incorrectly selects config.py as the scriptPath instead of the actual main file. Renaming the config file to _config.py or the main script to script.py fixes the issue. A prefixed main script that sorts before config.py parses as expected. I looked at the ExtensionParser.cs file on github and it curiously mentions this condition in a comment on line 925 but with an example that would sort before and not trigger the bug.
924 // If no script.* file found, look for any file with the target extensions
925 // This handles cases like BIM1_ArrowHeadSwitcher_script.dyn
In these cases the dot indicator is missing from the UI and only the config.py file will run as both the main and shift+click script. I confirmed the ConfigScriptPath and ScriptPath values from EXEC_PARAMS.script_runtime.ScriptData with various script naming.
I know there’s been an ton of work put into this new loader and the kinks are still being worked out so thought I’d bring it up here first incase it’s already been caught. Let me know if there’s any other detail you’d like from the testing I’ve done. And as always thank you all for your commitment to this community.