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
As titled, seems the moduleName is computed by the input/ output file name now, but it is not passed to the code generation function.
Requested to enhance this by adding another parameter in the CLI to support specifying the moduleName (and do no keep computing the module name, this is not working now, so it is safe to remove this for backward compatibility).
Proposed CLI parameter:
-n NAME, --module-name NAME The name of the generated parser object, namespace supported
The text was updated successfully, but these errors were encountered:
sammyhk
added a commit
to sammyhk/jison
that referenced
this issue
May 5, 2015
As titled, seems the moduleName is computed by the input/ output file name now, but it is not passed to the code generation function.
Requested to enhance this by adding another parameter in the CLI to support specifying the moduleName (and do no keep computing the module name, this is not working now, so it is safe to remove this for backward compatibility).
Proposed CLI parameter:
-n NAME, --module-name NAME The name of the generated parser object, namespace supported
The text was updated successfully, but these errors were encountered: