CudaFormatter 'format selection' is ok?

[Alexey-T]

Does CudaFmt expose 'format selection' ok? it does 'fmt sel' when selection is made and main cmd runs. is it like in VSCode/Sublime? maybe they expose separate cmd 'format selection' and usual 'format' always ignores the selection. in this case we can make CmdFmt like they.
@Hanatarou

PS. Sublime has not built-in formatter. it has 2-3 plugins for that. so each plugin can do it differently, so we can ignore ST.

[Hanatarou]

Hi @Alexey-T,

My point about rangeStart/rangeEnd is specific to Prettier's design, not a critique
of CudaFmt's architecture.

Key point:

Prettier MUST receive the entire file for proper formatting (that's why I use
force_all=1 in the plugin). Passing only a selection to Prettier would break it -
it needs full context to parse the AST correctly.

However, Prettier supports formatting only a RANGE within that full file via
--range-start / --range-end flags. The plugin should expose these options so users
can configure ranges in their .prettierrc or plugin config.

This is not about CudaFmt needing to change how it works. CudaFmt's current
behavior is perfect for Prettier - it already passes the full file with force_all=1.

The rangeStart/rangeEnd options are just Prettier-specific configuration that users
might want to set in their config files for specific use cases.

No changes needed to CudaFmt framework IMHO.

Best regards,

Hanatarou

[Alexey-T]

This sounds right, thank you.