fix(client): use @freecodecamp/strip-comments for js comments #42254
Conversation
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
|
|
github-actions
bot
added
the
platform: learn
Contributor
Author
|
@moT01 I'm sure I've not broken Safari this time, but if you could give a look that would be awesome. |
Contributor
|
LGTM But it would be nice to get a positive confirmation that nothing is broken in Safari. |
moT01
approved these changes
May 31, 2021
Member
moT01
left a comment
moT01
left a comment
There was a problem hiding this comment.
LGTM 🎉 Played around with a number of different types of lessons in Safari - nothing seemed broken.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Checklist:
Update index.md)mainbranch of freeCodeCamp.This reverts #42103, switches to @freecodecamp/strip-comments and ignores the type issues (for now).
Closes freeCodeCamp/strip-comments#10