feat: add multi-language formatters for native platform code

[realmeylisdev]

Summary

Adds formatting and linting support for non-Dart languages in templates, addressing #127.

• Kotlin: ktlint v1.5.0 for Android files
• Swift: SwiftFormat for iOS/macOS files
• C++: clang-format for Windows/Linux files

Changes

New Configuration Files

File	Purpose
.editorconfig	Shared editor settings (indent, line endings, etc.)
.swiftformat	SwiftFormat configuration for Swift files
.clang-format	clang-format configuration for C++ files

New Reusable Workflows

• kotlin_format.yaml - Kotlin linting with ktlint
• swift_format.yaml - Swift formatting with SwiftFormat
• cpp_format.yaml - C++ formatting with clang-format

Updated Template Workflows

Template	Format Checks Added
very_good_core	Kotlin, Swift (macOS job), C++
very_good_flame_game	Kotlin, Swift (macOS job), C++
very_good_flutter_plugin	Kotlin, Swift (macOS job), C++
very_good_wear_app	Kotlin (Android-only)

Test Plan

• CI workflows pass for all templates
• Kotlin formatting check runs on Android builds
• Swift formatting check runs on iOS/macOS builds (separate macOS runner)
• C++ formatting check runs on Windows/Linux builds
• No functional changes to generated template code

Closes #127

[realmeylisdev]

@marcossevilla I think I got it right correct now. Please review!

[marcossevilla]

Hey @meylis1998, I’ve had a chance to look over this. I think we might be overthinking the formatting in the workflows. Wouldn’t it be simpler to start with some research if there’s already a workflow in place for this?

Also, are the formatting configurations standardized? I was thinking, before adding formatting to each platform, we should first add one at a time and check out the standard configurations for each formatter before making any changes.

[realmeylisdev]

Hey @meylis1998, I’ve had a chance to look over this. I think we might be overthinking the formatting in the workflows. Wouldn’t it be simpler to start with some research if there’s already a workflow in place for this?

Also, are the formatting configurations standardized? I was thinking, before adding formatting to each platform, we should first add one at a time and check out the standard configurations for each formatter before making any changes.

Hey @marcossevilla, thanks for the review! You raise good points.

On existing workflows: You're right to ask. I checked and there's no existing workflow for Swift/Kotlin/C++ formatting - only Dart. However, I did create reusable workflows (swift_format.yaml,
kotlin_format.yaml, cpp_format.yaml) but I'm not actually using them via workflow_call. Instead, the logic is duplicated inline in each template workflow. That's inconsistent and should be fixed.

On standardized configurations:

• .clang-format uses Google style (industry standard ✅)
• .swiftformat uses 4-space indent which matches Apple conventions, but the rest is custom
• ktlint relies on .editorconfig with minimal Kotlin-specific settings

I should research the canonical/default configurations for each formatter before customizing.

On adding one at a time: Agreed. This PR required 8 fix commits after the initial implementation, which suggests it's too broad. I'll split this into separate PRs:

1. Swift formatting first
2. Kotlin formatting second
3. C++ formatting third

This will also let us validate each formatter's config against the standard before moving on.

I'll also look into existing GitHub Actions (like jidicula/clang-format-action) that might simplify the workflows.

[marcossevilla]

@meylis1998 are you okay closing this in favor of the following PRs breaking down each formatter?

[realmeylisdev]

@meylis1998 are you okay closing this in favor of the following PRs breaking down each formatter?

if you'd like me to resolve them one by one and you'll eventually give it a merge then I can do it either way I'm okay with closing it, appreciate your attention @marcossevilla

[realmeylisdev]

I see all the CI erros now resolved

[marcossevilla]

@meylis1998 are you okay closing this in favor of the following PRs breaking down each formatter?

if you'd like me to resolve them one by one and you'll eventually give it a merge then I can do it either way I'm okay with closing it, appreciate your attention @marcossevilla

@meylis1998 yes, that would be the approach I'd like to follow 👍