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
Just realised I need to rather use the module syntax, and found a few issues that needed to be rectified to get the script to run... sorry I don't currently have a PR for these, I'll do one as soon as I get a chance, but I thought it easier to let you know in case you have time before me.
Need to add var fs = require('fs'); at the top of tsgen.js file, or you get fs undefined error.
var config = argvToConfig; line should be var config = argvToConfig(); to actually execute the function.
Documentation states output folder is specified with --output but it actually has to be --outputFolder.
In argvToConfig function, check at the end should be if (!config.inputFileName || !fs.existsSync(config.inputFileName)) { instead of if (!inputFileName || !fs.existsSync(inputFileName)) {
In tsgen-core.js, there is a reference in the processRawMetadata function to config.baseClassName, but the property is actually config.baseClassFileName
use of a base class is not working,
Otherwise it's a really great tool. One question though, would it not be better to make it one tool with an option for module or entity syntax output? Surely make it easier to maintain? I haven't had to check enough the differences, so that may well be a stupid idea for various reasons, just a thought.
Thanks!
The text was updated successfully, but these errors were encountered:
Hey guys,
Just realised I need to rather use the module syntax, and found a few issues that needed to be rectified to get the script to run... sorry I don't currently have a PR for these, I'll do one as soon as I get a chance, but I thought it easier to let you know in case you have time before me.
var fs = require('fs');
at the top of tsgen.js file, or you get fs undefined error.var config = argvToConfig;
line should bevar config = argvToConfig()
; to actually execute the function.argvToConfig
function, check at the end should beif (!config.inputFileName || !fs.existsSync(config.inputFileName)) {
instead ofif (!inputFileName || !fs.existsSync(inputFileName)) {
processRawMetadata
function toconfig.baseClassName
, but the property is actuallyconfig.baseClassFileName
Otherwise it's a really great tool. One question though, would it not be better to make it one tool with an option for module or entity syntax output? Surely make it easier to maintain? I haven't had to check enough the differences, so that may well be a stupid idea for various reasons, just a thought.
Thanks!
The text was updated successfully, but these errors were encountered: