Uh oh!
There was an error while loading. Please reload this page.
[Fix] Fix styles of hbs files - #1722
Merged
Merged
Conversation
ghost
requested a review
from fhembergerJuly 9, 2018 07:46
fhemberger
approved these changes
Jul 9, 2018
fhemberger
approved these changes
Jul 9, 2018
fhemberger
left a comment
Contributor
There was a problem hiding this comment.
Little nit: You could remove the second space (after }}).
Because there are something wrong in formation, and when we run `npm run test` we cannot continue. This is the fixture for that.
ghost
commented
Jul 9, 2018
Author
OK, done. Thanks for tips |
fhemberger
commented
Jul 9, 2018
Contributor
Thanks! |
ghost
deleted the
FixStyleErr
branch
July 9, 2018 09:26
This was referenced Mar 18, 2022
This was referenced Apr 3, 2022
This was referenced Aug 24, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Because there is something wrong in formation, and when we run
npm run testwe cannot continue：This is the fixture for that：