Skip to content
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

access raw unparsed command ? #344

Open
whatsdis opened this issue Jul 10, 2019 · 1 comment
Open

access raw unparsed command ? #344

whatsdis opened this issue Jul 10, 2019 · 1 comment

Comments

@whatsdis
Copy link

sending a command with a value like : ['//a[@id="pagination"]/a[5]',3]

results in

[\'//a[@ id=\'pagination\' ]/a[5]\',3]

This has been causing a lot of problems, is there a way to turn off this auto-escaping or accessing the unparsed raw command?

@igorclark
Copy link

Hi folks, just picking up Vorpal and finding this a problem too (although Vorpal is pretty amazing otherwise!).

I want to do variadic arguments to capture whole strings with arbitrary characters, but any time the string contains a " the parsing breaks because vorpal.command() has stripped out the quotes.

It works fine when I run it as a vorpal.mode() - the whole string is passed straight through, as expected, including the quotes - but I want it as a command so it can be part of the history.

Any ideas how to turn this off, or if it's not intentional then where I can look around in the source in case I can fork and modify?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants