-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introducing bash-parser dependency #112
base: master
Are you sure you want to change the base?
Conversation
src/preparser.js
Outdated
// const preparser = function (input) { | ||
// input = parseEnvVariables(input); | ||
// return input; | ||
// }; | ||
|
||
module.exports = preparser; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we will use it, bash-parser has already taken care of env parameter expansion at this point, so the preparser should be superflous
We're tearing apart Vorpal right now anyway, so I think it would be a good idea to play with i there. |
@@ -10,6 +10,7 @@ var expand = require('./../util/expand'); | |||
|
|||
var head = { | |||
exec: function exec(args, options) { | |||
console.log({ args: args }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why would you want this?
This is an investigatory PR to study the introduction of a POSIX compliant shell code parser using bash-parser.
I studied the cash workflow, and I think the majority of changes in source code would concern Vorpal.
They could be implemented directly there (in vorpal core) or we could patch vorpal and implement it only for cash.