api-notebook
api-notebook copied to clipboard
mulesoft
Auto-open inspector
Can we stop with the auto-opening of the inspector? It's mostly frustrating, especially when you use a function that returns the global (e.g. window). It's huge and takes up like 3 screens.
Um, I don’t think so… are you seeing a lot of usecases we’ve not seen before that have this issue? Because in the usecases I see, it’s actually good to open it.
On Nov 18, 2013, at 12:29 PM, Blake Embrey [email protected] wrote:
Can we stop with the auto-opening of the inspector? It's mostly frustrating, especially when you use a function that returns the global (e.g. window). It's huge and takes up like 3 screens.
— Reply to this email directly or view it on GitHub.
I've personally just found it to be annoying in most cases. Mainly because not every cell I want to even see the result and some result objects are pretty large which makes it kind of disorienting to have a massive list appear. It's only a suggestion, but I don't have an issue if it's working for you.
It could also be the fact that I regularly have a fairly small browser window and have some form of OCD where I need them to be closed :wink:
Could we have cases in which the inspector isn’t auto-opened because we can see that it wouldn’t be useful (e.g. the API.createClient), or in other cases where it’s too big to display and maybe we have either a “more…” link or we don’t auto-open and indicate why in some way (click to expand this large object)?
On Nov 18, 2013, at 1:42 PM, Blake Embrey [email protected] wrote:
It could also be the fact that I regularly have a fairly small browser window and have some form of OCD where I need them to be closed
— Reply to this email directly or view it on GitHub.
A "more" link for objects greater than n lines seems like a good compromise to me.
