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

Pub build should support output that can be consumed by the Editor #15018

Closed
munificent opened this issue Nov 11, 2013 · 14 comments
Closed

Pub build should support output that can be consumed by the Editor #15018

munificent opened this issue Nov 11, 2013 · 14 comments
Assignees
Labels
type-enhancement A request for a change that isn't a bug

Comments

@munificent
Copy link
Member

This is mainly for the Editor's benefit but could be useful for users too. But it would be helpful if pub build displayed the name of the build directory it outputs to. That way the Editor can use that to know which directory in the user's workspace contains generated files which shouldn't be modified without having to hardcode the name of some output directory.

@danrubel
Copy link

Structured output (json?) would be best for editor with a section of content that should be displayed to the user in the editor console. Perhaps a --format=json option for this that editor could use to notify pub of the format it needs.

@munificent
Copy link
Member Author

Perhaps a --format=json option

Yup, that's what I was thinking too.

@munificent
Copy link
Member Author

Marked this as blocking #15829.

@munificent
Copy link
Member Author

Added Started label.

@munificent
Copy link
Member Author

Set owner to @munificent.
Added Triaged label.

@keertip
Copy link
Contributor

keertip commented Jan 15, 2014

Bob,

Right now pub build always puts the generated files in "build" directory. So would this change the behavior and users can now specify out folder?

@munificent
Copy link
Member Author

This bug is a bit murky, but there's two things in here:

  1. Having pub build print the path to the build directory.
  2. Have an option to make all of pub build's output be JSON.
  3. An option to specify a build directory.

This bug really only asks for the first two. Specifying an output directory is useful too, but that would be a separate bug.

@munificent
Copy link
Member Author

Changed the title to: "Pub build should support output that can be consumed by the Editor".

@munificent
Copy link
Member Author

Added Started label.

@munificent
Copy link
Member Author

Added Fixed label.

@munificent
Copy link
Member Author

You can pass in "--format json" to pub build now, and it will output a single JSON object to stdout.

@munificent
Copy link
Member Author

Jumped the gun a bit. Out for code review: https://codereview.chromium.org/184113007


Added Started label.

@munificent
Copy link
Member Author

Added Fixed label.

@DartBot
Copy link

DartBot commented Jun 5, 2015

This issue has been moved to dart-lang/pub#714.

@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed type-enhancement labels Mar 1, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

5 participants