`coldbox create handler --boxlang` / `--noboxlang` flag not propagated to view generation

[edyionescu]

What are the steps to reproduce this issue?

1. Create a BoxLang app: coldbox create app myApp --boxlang
2. Create a handler with the CFML flag: coldbox create handler myHandler --noboxlang
3. Observe the generated view file extension

What happens?

The handler and integration test correctly respect the --noboxlang flag (generating .cfc files), but the view is generated with the project's default extension (.bxm) instead of the requested .cfm:

INFO   Created View [app\views\myHandler/index.bxm]
INFO   Created Handler [app\handlers\myHandler.cfc]
INFO   Created Integration Spec [tests\specs\integration\myHandlerTest.cfc]

The same issue occurs in reverse: in a CFML app (--cfml), running coldbox create handler myHandler --boxlang generates a .cfm view instead of .bxm, while the handler and test correctly get .bx extensions.

What were you expecting to happen?

The view file extension should match the language flag passed to create handler. With --noboxlang, the view should be index.cfm, and with --boxlang, it should be index.bxm.

Any logs, error output, etc?

No errors, the wrong file is silently created. The workaround is to manually delete the incorrect view and run coldbox create view myHandler/index --noboxlang (or --boxlang) explicitly afterward.

What versions are you using?

Operating System: Windows 11 Pro 25H2
Package Version: 8.12.0+30