Debugging Library Code (New IDE)

[MS Amdani]

Hi,

Is it that I am missing something or what but I am unable to get into library code while debugging in the new IDE.

For example, in the parent script, we have a function which calls a library function:

//parent script

function parentFun( )

{

  MyLib.addSomething( );

}

//---------------------------------------------

//library script

function addSomething( )

{

  console.log("step1");

  console.log("step2");

  console.log("step3");

}

//library script code ends

Now, when debugging parentFun( ) I have added a breakpoint at:

MyLib.addSomething( )

It reaches to this point and from there I click on the Step-In button on the right panel in the new IDE and it simply executes the full function code, rather than getting to the 1st statement of this library function so I can see different variables and catch the issue.

Can anyone guide as to what I am missing.

Thanks.

[Andrew Roberts]

You are right. The new IDE cannot step into the libraries. Personally I've just stuck with the old IDE, and I hope they never turn it off. The new one is pretty and has some handy features, but too much has been lost.

--
You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/144bab00-300c-4ccf-b0b5-27cf200367afn%40googlegroups.com.

[MS Amdani]

Thanks for the confirmation...

I really could not believe myself when I could not debug that initally... as to how they could miss that out while upgrading the IDE.

Anyway, I have filed the issue on issue tracker here:

https://issuetracker.google.com/issues/189726432

[Alan Wells]

When I visit the Issue Tracker link at:

https://issuetracker.google.com/issues/189726432

I get a message that Access is denied.  Did you make a private issue?

On Tuesday, June 1, 2021 at 2:23:39 PM UTC-4 MS Amdani wrote:

Thanks for the confirmation...

I really could not believe myself when I could not debug that initally... as to how they could miss that out while upgrading the IDE.

Anyway, I have filed the issue on issue tracker here:

https://issuetracker.google.com/issues/189726432

On Tuesday, June 1, 2021 at 2:39:23 PM UTC+5 and...@roberts.net wrote:

You are right. The new IDE cannot step into the libraries. Personally I've just stuck with the old IDE, and I hope they never turn it off. The new one is pretty and has some handy features, but too much has been lost.

You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.

[Sohail]

Nope, and strange but I didn't set anything like that and neither do I find any setting now to set visibility for public / private views.

Perhaps, either that I posted it in some other category or Google team may have set it to private for some reason.

Here is the snapshot.

If you know how to get it set to public view please share.

Thanks.

--
You received this message because you are subscribed to a topic in the Google Groups "Google Apps Script Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-apps-script-community/0tPq4HMF7S0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/18f0d16b-4e83-453f-ad5a-4ca995cf3bbbn%40googlegroups.com.

[MS Amdani]

It looks as if this issue reported in another main apps script category has public visibility.

https://issuetracker.google.com/issues/190230379

Thanks.

[Alan Wells]

And that issue is a duplicate of:

https://issuetracker.google.com/issues/167903155