Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

introduces force-use-flutter argument for commands #178

Merged

Conversation

devmil
Copy link
Member

@devmil devmil commented Mar 10, 2024

Description

This PR adds a new argument for dart_apitool commands: force-use-flutter.
This optional argument allows the user to force dart_apitool to use the flutter command.

Without this flag being set dart_apitool tries to determine the tool to use by inspecting the pubspec.yaml of the package.
There are some conditions (e.g. dependencies that need Flutter while the package under investigation only needs Dart) that make it necessary to override this automatic detection.

Type of Change

  • 🚀 New feature (non-breaking change)
  • 🛠️ Bug fix (non-breaking change)
  • ⚠️ Breaking change (feature or bug fix which breaks existing behaviors/APIs)
  • 🏗️ Code refactor
  • ⚙️ Build configuration change
  • 📝 Documentation
  • 🧹 Chore / Housekeeping

fixes #177

@devmil devmil changed the title introduces override-use-flutter argument for commands introduces force-use-flutter argument for commands Apr 5, 2024
@devmil devmil merged commit 890f68b into main Apr 5, 2024
11 checks passed
@devmil devmil deleted the feature/introduce_override-use-flutter_argument_to_commands branch April 5, 2024 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Flutter recognition not working for transitive dependencies
2 participants