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

An asset whose path is a prefix of another should cause a collision #17150

Closed
munificent opened this issue Feb 26, 2014 · 2 comments
Closed

An asset whose path is a prefix of another should cause a collision #17150

munificent opened this issue Feb 26, 2014 · 2 comments
Labels
area-pkg Used for miscellaneous pkg/ packages not associated with specific area- teams.

Comments

@munificent
Copy link
Member

Since barback doesn't have a concept of directories, it's possible to emit two assets like:

foo/bar // a file "bar" with no extension
foo/bar/baz.txt

That will fail horribly with something like pub build when it tries to output those two files. Instead of allowing this, barback should probably treat that like a collision.

@lrhn
Copy link
Member

lrhn commented Feb 27, 2014

Added Area-Pkg label.

@munificent munificent added Type-Defect area-pkg Used for miscellaneous pkg/ packages not associated with specific area- teams. labels Feb 27, 2014
@DartBot
Copy link

DartBot commented Jun 5, 2015

This issue has been moved to dart-archive/barback#36.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-pkg Used for miscellaneous pkg/ packages not associated with specific area- teams.
Projects
None yet
Development

No branches or pull requests

4 participants