Skip to content

No debug break by default implementation added for iOS and Android #1801

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

Merged
merged 1 commit into from
Jun 6, 2016

Conversation

enchev
Copy link
Contributor

@enchev enchev commented Jun 3, 2016

Related to #1376

When you call tns debug ios|android (no --debug-brk) now we will build, deploy and start the application and attach the debugger. You can debug normally by placing breakpoint(s) in desired file(s). If you want to break somewhere initially you can use debugger keyword in your code.

The --debug-brk switch is still working as before in case you want to use it (not sure for what reason).

@enchev enchev changed the title No break by default implementation added for iOS and Android No debug break by default implementation added for iOS and Android Jun 3, 2016
@rosen-vladimirov
Copy link
Contributor

rosen-vladimirov commented Jun 3, 2016

You should update help content and documentation as well (as I believe we are changing the default behavior of command).

this.startAppWithDebugger(packageFile, packageName).wait();
//TODO: Find different way to make sure that the app is started.
sleep(500);
this.attachDebugger(device.deviceInfo.identifier, packageName).wait();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe I'm totally missing something here, but shouldn't startAppWithDebugger do this... Based on it's name it looks like that's what it should do and we do not have to attach debugger again?
What's the case here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dunno, you tell me?

@enchev
Copy link
Contributor Author

enchev commented Jun 6, 2016

Hey @vchimev @dtopuzov can you test the CLI behavior in this pull request and like if this is the expected?

@PanayotCankov
Copy link
Contributor

👍 for the iOS changes, you may ping @slavchev to review the Android part.

@enchev
Copy link
Contributor Author

enchev commented Jun 6, 2016

Hey @blagoev @slavchev do you have any comments about these changes?

@slavchev
Copy link

slavchev commented Jun 6, 2016

👍

@enchev enchev merged commit 95fd96b into master Jun 6, 2016
@enchev enchev deleted the debug-no-break branch June 6, 2016 08:04
@@ -1,6 +1,9 @@
debug android
==========

All you need to do to start debugging your app is to execute `tns debug android`. The NativeScript CLI will build, deploy, start your app, start Chrome DevTools and attach the debugger.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be under the Usage|Synopsis part of the help (here -> https://github.com/NativeScript/nativescript-cli/pull/1801/files#diff-e7b2eaa70b7b2394cb03e78ab260308aR18 ). We print the table of usage first in all of the help content.

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

Successfully merging this pull request may close these issues.

4 participants