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
It would also be nice to be able to add a line directly to kcode that's not a comment (without //). That would translate to a break in knitting and message on the kniterate screen and allow for on-machine debugging
could be worth having two separate node commands—one for a development environment that runs a 'debugging' version of the program (includes corresponding knitout lines as comments above each kcode pass; maybe some other features too), and then a production one (aka the current status quo).
Could either:
Use npm instead (so could have run command npm run debug [which would run node knitout-to-kcode.js && debug.js , with 'debug.js' being a separate file that contains only the additional debugging features] and npm run knitout-to-kcode.js [runs just node knitout-to-kcode.js] in package.json), or
Stick with using just node and make two separate files (so run command node debug.js [copy & paste original file for debug.js + add additional functions to that one] and node knitout-to-kcode.js).
For debugging, it would be useful to optionally include the original knitout code and/or line numbers as comments in the kcode file.
For example:
Might transform into something like:
The text was updated successfully, but these errors were encountered: