Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Pub package layout conventions don't apply well with Polymer applications #13991

Closed
DartBot opened this Issue Oct 10, 2013 · 7 comments

Comments

Projects
None yet
5 participants
Member

DartBot commented Oct 10, 2013

This issue was originally filed by @butlermatt


The package layout conventions as described in Pub documentation[1] do not apply readily to Polymer applications. Where should component implementation files exist? Do implementation Polymer .html files belong in lib/src/ ? Do they belong in web/src/ ? what about their associated dart scripts/classes?

If they do belong in lib/src/ then this may also be BlockedOn Issue #12867

Contributor

kasperl commented Oct 14, 2013

Added Area-Polymer, Triaged labels.

Member

sigmundch commented Oct 14, 2013

Bob/Nathan - what are your thoughts on this?


Removed Area-Polymer label.
Added Area-Pub label.

Member

munificent commented Oct 14, 2013

Let's discuss this in person when Nathan is around. I'm not sure what we want to do here either.

Member

munificent commented Jan 6, 2014

Removed Priority-Unassigned label.
Added Priority-Medium label.

Member

munificent commented Feb 8, 2014

Marked this as being blocked by #16647.

Member

munificent commented Feb 11, 2014

We spent some time talking about this and we've decided that we will officially support non-Dart files in "lib". I think the main missing piece now is updating the docs to reflect this.

Some notes on the discussion here: https://gist.github.com/munificent/8873127


cc @nex3.
Set owner to @Sfshaza.
Removed Area-Pub label.
Added Area-Documentation label.

Sfshaza commented Mar 27, 2014

I've tweaked the "Assets and Transformers" page with regards to where assets can go:
https://www.dartlang.org/tools/pub/assets-and-transformers.html#where-to-put-assets


Added Fixed label.

@Sfshaza Sfshaza was assigned by DartBot Mar 27, 2014

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment