On 09/10/2016 9:17 PM, Jinx wrote:
On Sunday, 9 October 2016 at 06:55:44 UTC, Mike Parker wrote:
On Sunday, 9 October 2016 at 05:34:36 UTC, Jinx wrote:
huh? Yes it is necessary. How hard could it be. Editing a script is
the same as editing the json file and creates junk files. Why make
things harder than they have to be? Seems like it would be rather
trivial to implement.
Harder is relative. You're talking about adding a maintenance cost to
dub for something that can be trivially done in a script. Regardless,
your best bet is to add an enhancement request to dub's issue list [1]
and see how it goes. Be sure to clarify if you're talking about
passing args to dub or to the target of `dub run`, or both.
[1] https://github.com/dlang/dub/issues
Come on, stop trying to be the asshole. You know as well as I do that it
would require nearly 0 maintenance. You act like this is rocket science
when really you are just being lazy.
With your logic there is no reason to do anything because everything
requires some non-zero maintenance cost. I have to maintain my script
too, that is non-zero.
The dub source code already has all the machinery required(parsing the
dub json file and parsing the commands) so it would require very little
code and require very little maintenance and provide a huge benefit for
complex command line arguments and allow those command lines to
propagate with the project file instead of the user having to provide a
potentially security hole by passing around script files.
See, you can't win because you are wrong.
That is enough.
Mike Parker has presented a workaround that you can implement.
He has also shown how you can contact those that have the power to make
this happen as you desire.
But as shown by other related issues[0], you may not get what you want.
[0] https://github.com/dlang/dub/issues/940
