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.

Sign up for GitHub

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

Jump to bottom

feat(visit): should parseVisit() exists? #6

Open

kwonoj opened this issue Jul 28, 2023 · 1 comment

Owner

kwonoj commented Jul 28, 2023 •

edited

Techinically, it is possible to have a wrapping interface to parse itself, such as

parseVisit<T = Record<string, any>>(source: string, parseOptions: {}, visitor?: Visitor): Promise<T>

When you have an input as source code string and do not need separate steps to parse in JS first. Unclear if it's needed though.

The text was updated successfully, but these errors were encountered:

Owner Author

kwonoj commented Jul 28, 2023

or in other way, should parseVisit only exists and current visit won't be needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment