-
Notifications
You must be signed in to change notification settings - Fork 290
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
Update to handlebars v5 #1971
Update to handlebars v5 #1971
Conversation
return Err(RenderError::new( | ||
return Err(RenderErrorReason::ParamNotFoundForIndex( | ||
"{{team-text}} must have at least two parameters", | ||
)); | ||
0, | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This wasn't a hard error, only a deprecation warning. I hope the variants I chose make some sense. It's a bit late.
@@ -137,6 +137,5 @@ fn main() { | |||
src="/static/images/ferris.gif" /> | |||
</div> | |||
</section> | |||
{{> components/tools/install-script }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file was removed in a commit from 2019. It seems that until now, handlebars silently ignored the missing component. I believe the new error was introduced in this PR The result was that the server would crash on the get-started page and the user would see a 404.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I clicked trough a bunch of the pages on the website looking for other occurrances, but couldn't find any. I could've missed something though.
We should carefully check staging before deploying this one. But it should be fine |
closes #1918