17

Back in May 2016 @canon implemented several useful options in the Stack Snippets console script (there's a demo here). Please

  1. Deploy the updated script so those options can be used (currently, only maxEntries works), and

  2. Add a UI for them so people don't use console.config directly, or resort to adding irrelevant CSS to their answers (like this). Or at least support hand-edited options in the snippet comment markup in the short term before a UI is available.

On the UI, I'd suggest making it a Console Options button or some such that shows options driven by the script itself, so that when an option is added to the script, the UI for it can be added at the same time so we don't have multi-month lag between implementation and availability. The options would be serialized to JSON and inserted in the stack snippet's introductory comment node.

For instance, where a snippet might currently start with this:

<!-- begin snippet: js hide: false console: true -->

If the user uses the dialog to set options, it might look like this:

<!-- begin snippet: js hide: false console: true console-options: {"maximize":true,"autoScroll":false} -->

Those options get converted into a hidden call to console.config at the beginning of the snippet script.


(I raised this at the time but as nothing's happened and you can't bounty an answer, I'm posting a proper .)

  • Heh, I never saw this feature request. :/ – canon Jan 8 '18 at 7:56
  • There's a more recent version with lazy console expansion (like browsers), but canon's still working out bugs in it, so we'll update this FR when it's ready. – T.J. Crowder Jan 8 '18 at 8:21

You must log in to answer this question.

Browse other questions tagged .