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

add htmlEntryPoint option to transformer #11

Merged
merged 2 commits into from
Jan 23, 2015
Merged

Conversation

jakemac53
Copy link
Contributor

fixes #10

@jakemac53 jakemac53 force-pushed the html-entry-point branch 2 times, most recently from 5c3ad15 to 9399106 Compare January 21, 2015 17:49
@@ -65,12 +69,23 @@ class InitializeTransformer extends Transformer {
if (newEntryPoint == null) {
newEntryPoint = entryPoint.replaceFirst('.dart', '.bootstrap.dart');
}
return new InitializeTransformer(entryPoint, newEntryPoint);
var htmlEntryPoint = settings.configuration['htmlEntryPoint'];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we could do the change from 'htmlEntryPoint' -> 'html_entry_point' right away or separately (issue #14)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can update all of these at once later

@sigmundch
Copy link
Contributor

lgtm

@jakemac53
Copy link
Contributor Author

submitting for now, we can revisit the allowing entry points in different folders thing in a later cl if its needed

jakemac53 added a commit that referenced this pull request Jan 23, 2015
add htmlEntryPoint option to transformer
@jakemac53 jakemac53 merged commit b0645a4 into master Jan 23, 2015
@jakemac53 jakemac53 deleted the html-entry-point branch January 23, 2015 20:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Add transformer option to rewrite original entry point script tag
2 participants