Skip to content
This repository has been archived by the owner on Jan 20, 2018. It is now read-only.

Support supplying only an htmlEntryPoint #13

Closed
jakemac53 opened this issue Jan 21, 2015 · 4 comments
Closed

Support supplying only an htmlEntryPoint #13

jakemac53 opened this issue Jan 21, 2015 · 4 comments

Comments

@jakemac53
Copy link
Contributor

Assuming there is only one dart script tag, and it lives in the same library as the html file, we can just use that dart file as the entry point and not require it to be specified:

transformers:
- initialize:
    entryPoint: web/index.dart
    htmlEntryPoint: web/index.html

becomes just:

transformers:
- initialize:
    htmlEntryPoint: web/index.html
@jakemac53
Copy link
Contributor Author

we could also possibly just use entryPoint but allow you to pass an html file instead of a dart file, and then do the right thing based on the file extension

@sigmundch
Copy link
Contributor

How about we do this by hiding this transformer inside another transformer in web_components?

If you write:

transformers:
- web_components/initialize:
    entry_point: web/index.html

@sigmundch
Copy link
Contributor

ah- never mind, I thought initially this was for specifying the entry point for html-initialization, not just plain initialization. Now that I see #10, I see that this was just to update the bootstrap.html

@jakemac53
Copy link
Contributor Author

fixed in 8ff3cf3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants