You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most likely there are many better solutions for this, but here it is my quick attempt.
Usage: md.extract-js.js markdown-file.md.
Extracted .js files will be created in the markdown-file.md.extracted-js directory next to markdown-file.md. Each file has this name template: numberOfFragment.numberOfFirstLine-numberOfLastLine.js.
A contributor can run a linter on the whole directory or run each file with Node.js. There will be many linter errors or runtime errors due to many undeclared (or unused) variables, so some filter work will be needed.
In our case, the odd filenames are bad examples, the even filenames are good ones.
Hey this is a cool script! This could be expanded upon to be used as part of a code testing suite too for this project. I think having real working code here is a thing to aim for!
Uh oh!
There was an error while loading. Please reload this page.
Most likely there are many better solutions for this, but here it is my quick attempt.
Usage:
md.extract-js.js markdown-file.md
.Extracted
.js
files will be created in themarkdown-file.md.extracted-js
directory next tomarkdown-file.md
. Each file has this name template:numberOfFragment.numberOfFirstLine-numberOfLastLine.js
.A contributor can run a linter on the whole directory or run each file with Node.js. There will be many linter errors or runtime errors due to many undeclared (or unused) variables, so some filter work will be needed.
In our case, the odd filenames are bad examples, the even filenames are good ones.
Here is a new PR from this script's work.
The text was updated successfully, but these errors were encountered: