[pigeon] make swift enum CaseIterable

[HannesGitH]

instead of generating

enum FooEnum: Int {
  case foo = 0
  ...

we will now generate

enum FooEnum: Int, CaseIterable {
  case foo = 0
  ...

allowing consumers to use FooEnum.allCases to iterate over all possible enum values in swift platform code

fixes flutter/flutter#186447

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[gemini-code-assist]

Code Review

This pull request updates Pigeon to version 26.3.5 and adds CaseIterable conformance to generated Swift enums. Feedback indicates that the change lacks necessary tests or golden file updates to verify the generated code, as required by the style guide.

[gemini-code-assist]

The addition of CaseIterable to generated Swift enums is a useful improvement. However, I noticed that no new tests or updates to existing golden files were included in this pull request to verify this change. Please ensure that the generated output is covered by tests to prevent regressions and verify the correct syntax is produced.

[HannesGitH]

it is now included in test

[tarrinneal]

please run the formatting tool (should run automatically after the generate tool) and re-upload so I can see the actual changes.

[HannesGitH]

@tarrinneal

➜  pigeon git:(186447-pigeon-swift-enum-caseiterable) ✗ dart run tool/generate.dart
Generating platform_test/ output...
Generation complete!
Generating example/ output...
Generation complete!
Formatting generated output...

and we have still a bunch of formatting changes in swift and header files, should I run something else?

Dart SDK version: 3.11.4 (stable) (Tue Mar 24 01:02:20 2026 -0700) on "macos_arm64"

[tarrinneal]

@tarrinneal

and we have still a bunch of formatting changes in swift and header files, should I run something else?

I've pulled down, regenerated, and formatted the code for this PR. You can merge those changes from this branch