-
Notifications
You must be signed in to change notification settings - Fork 150
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
Allow for AwaitDebugger but don't pause on first #589
Comments
Hi @BinarySpike,
Interesting. Can you describe a situation in which this capability would be useful? To put it another way, why is
Well, we wouldn't want to make the API too clunky – e.g., Thanks! |
@BinarySpike Hey Nathan small world its Todd, what you using ClearScript for? |
Two issues, first if I
That would be my preference. Seems the logical solution.
@wysisoft ! Mostly looking at it for a hobby project. However, I'm looking at exposing a partial API of our application layer so that we can implement configurable business logic. We have a system that manages tons of files & folders and each tenant uses the system differently. Being able to deploy a tenant, then build them a script where they can enter properties, then hit a button and the script creates files, creates folders, and applies permissions based on their specific needs would be chefs kiss 😗👌 |
Hi, i would also like this. Kind regards, |
For performance/quality-of-life reasons, I'd like to wait for a debugger to attach, but not pause directly after.
See: https://github.com/microsoft/ClearScript/blob/1ba26876fc9dc1dd290fac657914cc1a8cf4c487/ClearScriptV8/V8IsolateImpl.cpp#L737C1-L737C25
Would adding a flag and skipping the identified line be a reasonable way to implement this?
The text was updated successfully, but these errors were encountered: