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

htmlOutputTemplate bug #304

Merged
merged 1 commit into from
Nov 18, 2015
Merged

htmlOutputTemplate bug #304

merged 1 commit into from
Nov 18, 2015

Conversation

johnman
Copy link
Contributor

@johnman johnman commented Nov 6, 2015

After moving from 4.x to 5.1 I noticed that the html template stopped working. I pulled down the source and tracked down the issue. It looks like htmlOutputTemplate was missing from the delayTemplateExpansion array and grunt would replace the placeholders as it would try and resolve them (so your generated html.ts files would not have the html content). I looked to add a test but it looks like one was added but not being run correctly (it needed the html settings within the options object and the settings and expected template needed some tweaks to get the diff passing. As I was preparing this pull request I noticed someone else had also picked up on this issue as well.

After moving from 4.x to 5.1 I noticed that the html template stopped working. I pulled down the source and tracked down the issue. It looks like htmlOutputTemplate was missing from the delayTemplateExpansion array and grunt would replace the placeholders as it would try and resolve them (so your generated html.ts files would not have the html content). I looked to add a test but it looks like one was added but not being run correctly (it needed the html settings within the options object and the settings and expected template needed some tweaks to get the diff passing. As I was preparing this pull request I noticed someone else had also picked up on this issue as well.
@rolego
Copy link

rolego commented Nov 13, 2015

What's the problem here?:
There are several pull requests pending or already merged related to this bug. But just nothing happens since weeks. I would appreciate if the fix could be released soon.

See also:
#298
#291
#307
#304

nycdotnet added a commit that referenced this pull request Nov 18, 2015
@nycdotnet nycdotnet merged commit 44f52dc into TypeStrong:master Nov 18, 2015
@nycdotnet
Copy link
Contributor

Thanks so much for the PR. So sorry for the delay.

@johnman
Copy link
Contributor Author

johnman commented Nov 18, 2015

No problem, Thanks for maintaining this project. Any chance we can a new npm version published too? I know it's not a huge change but it is a bug that is a showstopper for those that use this feature.

@nycdotnet
Copy link
Contributor

5.1.1 should be out on npm now

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

Successfully merging this pull request may close these issues.

3 participants