Remove the artificial limitation that prevents the extension from working with plain Dart projects
Sominemo opened this issue · 1 comments
Currently the extension will refuse to work in any project due to a function which enumerates all current workspaces and checks if the package depends on flutter.
Yet, the underlying library and the extension itself can work fine on a plain Dart project without Flutter dependency. I checked this by commending out the line which filters out workspaces that don't have flutter in pubspec.yaml.
It would be great if this limitation could be removed, or at least turned off using a flag in settings — since it's not a supported way to use the extension.
The Flutter Intl extension generates localization code that relies on specific Flutter functionalities. You can find more details in the l10n.dart and messages_all.dart generated files. Given the dependency on Flutter in the generated code, what specific benefits do you see in enabling this extension for plain Dart projects?
Similar issues: intl_utils#71