-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
playground: click on AST to view the corresponding code #30
Comments
For better UX, I would say it's worth it. Additionally, most of the loading time is for the wasm file. It can be implemented. You can refer to https://ast.sxzz.moe/ |
Yes, wasm loading often takes time. |
Could be worth it. I have more experience with Monaco than I do with codemirror, but if it's super problematic then we should. What are the downsides of a switch to codemirror? |
That's also why I suggest boshen to publish wasm to npm. We can even change the oxc version for testing regression issue. |
Given the complexity of the feature and its completion on ast.sxzz.moe, I might extract the AST Tree Viewer as a Vue component for easy reuse in oxc. |
In the previous playground, clicking on 'ast' could find the corresponding code, which was very comfortable to use, but it seems that the current new playground does not have it.
The text was updated successfully, but these errors were encountered: