-
Notifications
You must be signed in to change notification settings - Fork 129
Add option for setting arguments for tool compilation. #2576
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
Add option for setting arguments for tool compilation. #2576
Conversation
adffa69
to
b3c2caa
Compare
b3c2caa
to
dca9403
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, but the README should be updated with the new parameter.
Added to the README.md, and I changed the name from compile-args to compile_args, to match the other tags. |
README.md
Outdated
@@ -289,6 +289,7 @@ dartdoc: | |||
command: ["bin/drill.dart"] | |||
setup_command: ["bin/setup.dart"] | |||
description: "Puts holes in things." | |||
compile_args: ["-no-sound-null-safety"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably should have two dashes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my head, it did. :-) Fixed.
I started to convert a tool to null safety that had non-null-safe dependencies, and I realized that dartdoc will try and compile without the
--no-strong-null-safety
flag, and there was no way to specify it.This PR adds a mechanism for adding compile arguments to Dart-based tools, so that they can specify arguments like
--no-strong-null-safety
(or any other args).