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 package layout conventions don't apply well with Polymer applications #13991
Comments
Added Area-Polymer, Triaged labels. |
Bob/Nathan - what are your thoughts on this? Removed Area-Polymer label. |
Let's discuss this in person when Nathan is around. I'm not sure what we want to do here either. |
Removed Priority-Unassigned label. |
Marked this as being blocked by #16647. |
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. |
I've tweaked the "Assets and Transformers" page with regards to where assets can go: Added Fixed label. |
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
The text was updated successfully, but these errors were encountered: