add 'generate: true' to support in workspaces

[abikko]

Environment

• Dart version (run dart --version): Dart SDK version: 3.6.0 (stable) (Thu Dec 5 07:46:24 2024 -0800) on "macos_arm64"
• OS kind and version (e.g. "Windows 10, version 1809" or "macOS 12.4"): macOS 15.1.1
• Are you using the Chinese community mirror or a corporate firewall? - No

Problem

Currently, I have project which currently is using intl package,

and I generate messages from arb using the command 'flutter gen-l10n' with generate: true

but when I trying to run 'flutter pub get' in workspace - terminal giving me error 'generate: true is not supported within workspaces.'

So, I removed 'generate: true' in pubspec.yaml, and I have another error:
"Attempted to generate localizations code without having the flutter: generate flag turned on.
Check pubspec.yaml and ensure that flutter: generate: true has been added and rebuild the project. Otherwise, the localizations source code will not be importable."

name: admin
description: New Admin on Flutter
version: 1.0.0+1
publish_to: none

environment:
  sdk: ^3.6.0
resolution: workspace

dependencies:
  flutter:
    sdk: flutter
  flutter_localizations:
    sdk: flutter

dev_dependencies:
  build_runner: ^2.4.12
  flutter_test:
    sdk: flutter

flutter:
  uses-material-design: true
  assets:
    - assets/icons/
    - assets/

Expected behavior

Generate AppLocalizations - dart class

Actual behavior

Giving error
"Attempted to generate localizations code without having the flutter: generate flag turned on.
Check pubspec.yaml and ensure that flutter: generate: true has been added and rebuild the project. Otherwise, the localizations source code will not be importable."

[sigurdm]

Oh - this will not be trivial to support. This needs to be supported in the flutter tool

The tool could run dart pub workspace list to find all pubspecs, and iterate through them to see which to generate for.

In general I think we are considering moving away from the flutter: generate internationalization method.

I'd suggest using one of the alternative ways of generating internationalization support :
https://docs.flutter.dev/ui/accessibility-and-internationalization/internationalization#alternative-internationalization-workflows

[sigurdm]

cc @bkonyi

[sigurdm]

Linking to flutter/flutter#160151

[sigurdm]

Issue for deprecation of flutter_gen: flutter/flutter#102983

[abikko]

Thanks!

Helped this reply: flutter/flutter#160151 (comment)

[sigurdm]

Hmm - we should probably fix this in general, but nice that the workaround exists!

[bkonyi]

Yeah, the plan is to remove flutter_gen in a future release but I'm not sure what the timeline is on that (cc @matanlurey). If this is going to be a lot of work to support in pub workspaces, we should probably just direct users to migration documentation so they can move off this deprecated implementation.

[matanlurey]

I plan to disable it by default in the upcoming stable release (can still be opted-back into) and then removed in the following.