Skip to content

Conversation

@MakMuftic
Copy link
Contributor

Description

Based on the discussion ChainSafe/filsnap#88 and some further investigation, I realized that the problem origin is inside the library used for stripping comments. The problem occurs if there are double quotes inside the comment, and this issue has been created inside strip-comments lib (jonschlinkert/strip-comments#49). Unfortunately, this PR with the fix is stale for some time now, so inside our fork of snaps-cli we used a forked version of strip-comments library.

Changes

In this PR I replaced strip-comments with our fork that:

  • fixes a bug with double quotes inside the comment
  • already contains types, so no need for importing them

@rekmarks
Copy link
Member

rekmarks commented Jan 4, 2022

This looks great @MakMuftic, thank you! There appears to be a type-related build failure, internal to the forked package. My suspicion is that _parse is implicitly of type any per this line.

I'm ready to merge this as soon as CI passes.

@rekmarks
Copy link
Member

rekmarks commented Jan 7, 2022

Superseded by #189

@rekmarks rekmarks closed this Jan 7, 2022
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.

2 participants