Removed Type-Defect label.
Added Type-Enhancement, Area-Editor, Triaged labels.
Changed the title to: "Configure parameters to pub build in Dart Editor".

Set owner to @keertip.
Added this to the 1.4 milestone.
Removed Priority-Unassigned label.
Added Priority-Medium label.

Luke,

Users would like to run pub build in either debug or no debug mode. How can we specify this in the ui? Preference?

cc @lukechurch.

Removed this from the 1.4 milestone.
Added this to the 1.5 milestone.

Removed this from the 1.5 milestone.
Added this to the 1.6 milestone.

Removed this from the 1.6 milestone.
Added Oldschool-Milestone-1.6 label.

Added NotPlanned label.

Added this to the 1.6 milestone.

This comment was originally written by @0x3333

Must have...

This comment was originally written by @zoechi

You can just run pub build from command line to get the deployable result. Other deploy tasks are usually from command line (scripted) anyway.

This comment was originally written by ti.t...@unicbrasil.com.br

I know that, this is the way I do today. But it is a must have...

This comment was originally written by @zoechi

I think a "must-have" is an essential feature without any or only a cumbersome workaround.

I think you should at least provide some information about your workflow why the workaround doesn't work for you or why it is too cumbersome to use.

Otherwise in my opinion there are at least 1000 open issues more important than this one.

This comment was originally written by @0x3333

Agreed. No pressure.

This comment was originally written by @zoechi

According to comments on other issues/feature requests, the Dart teams intention seems to be to provide a good IDE for Dart.
If you want a full featured IDE (like a Swiss army knife) you should consider using other options like the Eclipse Dart plugin or one of the IntelliJ IDEs with Dart plugin, Sublime Text, ...

This comment was originally written by guohaola...@gmail.com

But if you're going to make a good IDE, and have already provided a pub build feature, why only build it halfway?

This comment was originally written by @zoechi

I'm not a Googler and this is just my private opinion.
A full-featured IDE is a huge project and requires a lot of ressources. There is no end to useful features one could add to and IDE. A great IDE would also support projects with mixed languages (Java, Go, ..., on the server side for example).
If Google would offer such a great IDE it would prevent others (like IntelliJ) to invest money in their own products because there is nothing to earn when there is already another great option for free.
And then a lot of people would complain that Google controls the whole ecosystem and vendor lock-in and what not (not a good starting point to motivate others to add Dart support to their browser).
Dart is an open source project and not Googles main business.
So of course they could, but why would they?

DartEditor is a great free option and Google ensures that there is room for alternatives - IMHO nothing to complain about.

This comment was originally written by @mezoni

Dart is an open source project and not Googles main business.

Adding some features not so hard as you can think.

Eg.

• Adding autocompletion for the keywors - not so hard
• Adding helper to create a library ("library" and "part of" scripts) - not so hard
• Adding helper to create a class script (as part of library) - not so hard
• Adding helper to rename a library name and update their "part of" scripts relative to the package root path - not so hard
• Adding configurable toolbar - not so hard
• Adding support of launch some 3rd party tools (tasks) - not so hard

Problem not in the Google. Problem in the Editor Team.
They have too many misconceptions and prejudices.

This comment was originally written by @0x3333

#­16:
Sorry, but I have to disagree.

To start with, this is just a feature request to a feature already implemented, it is just a flag in the config editor. We are not asking for a feature with a huge impact in the development.

We also understand that this is a non priority issue, no problems with that too. I can wait for this to be implemented. But as this is a open source project I also believe that is our role to complain about it, even contribute with patches(If we know how).

But, believing that they didn't do that to allow other vendors to do is absolutely wrong.

We don't have to settle with a "great free option". As users, we are pushing this tool forward. I build software in Dart for multinational companies. Google is earning money with that. There is no free lunch my friend.

One more time, I don't have problems waiting for this to be implemented, I have a workaround.

This comment was originally written by guohaola...@gmail.com

#­16 Dart is a great tool, no doubt about that, but the point of a great tool is so that you don't have to find a work around to do certain things, especially when trying to publish a release build.