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

Collaborate with us #15

Open
steelbrain opened this issue Oct 17, 2015 · 3 comments
Open

Collaborate with us #15

steelbrain opened this issue Oct 17, 2015 · 3 comments

Comments

@steelbrain
Copy link

I am the author of the linter package. We're thinking of writing a base debugging interface provider now. Your experience from this package will be very helpful. Would you mind sharing your ideas about how that base provider's API should look like and about it's UI?

@xndcn
Copy link
Owner

xndcn commented Oct 19, 2015

@steelbrain Sorry for may late reply...
Thank you, it's my honor!

When I design this package, this is my mainly reference: https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI.html
I think it's also helpful for you.

I think the most useful parts are:
breakpoint: add, delete, list...
watch variable: add, delete, list..
execution: run, stop, interrupt, continue, next, step...
They are important for both API and UI

@niclashoyer
Copy link

@steelbrain is there any issue in the linter repo that tracks the current discussion/state of the debugging API?

@steelbrain
Copy link
Author

@niclashoyer I am sorry but there isn't any discussion on a private repo yet, we did discuss it in a private atom slack channel but the last time I checked Joe FitzGerald had taken the responsibility of getting debugger up and running, he says he'll try to adopt the concepts from nuclide.

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

3 participants