Skip to content

pub transformer does not get access to pubspec.yaml as an asset #21574

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

Closed
DartBot opened this issue Nov 11, 2014 · 4 comments
Closed

pub transformer does not get access to pubspec.yaml as an asset #21574

DartBot opened this issue Nov 11, 2014 · 4 comments
Labels
closed-duplicate Closed in favor of an existing report

Comments

@DartBot
Copy link

DartBot commented Nov 11, 2014

This issue was originally filed by @paulevans


What steps will reproduce the problem?

  1. Write a transformer that attempts to use information in pubspec.yaml

What is the expected output? What do you see instead?
pubspec.yaml appears as asset
Actual:
pubspec.yaml never processed as asset

What version of the product are you using?
1.7.2

On what operating system?
Mac OS X

Please provide any additional information below.
Some metadata provided in the pubspec.yaml file (e.g. version. name, description) would be useful to some pub transformers

Work around:
On transformer construction current working directory is project root - so path can be constructed to pubspec.yaml at that point and read.

@DartBot
Copy link
Author

DartBot commented Nov 11, 2014

This comment was originally written by @zoechi


Similar to http://dartbug.com/21020

@kasperl
Copy link

kasperl commented Nov 12, 2014

Added Area-Pub, Triaged labels.

@nex3
Copy link
Member

nex3 commented Nov 12, 2014

Added Duplicate label.
Marked as being merged into #19434.

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

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

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate Closed in favor of an existing report
Projects
None yet
Development

No branches or pull requests

4 participants