question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Breaking: Changes to Output Window

See original GitHub issue

Nothing here is set in stone, tagged with help wanted to get extra user input

Please keep comments related to this issue. Want something else adding/sorting? Please open a new issue


To do list

  • Confirm implementation
  • Apply confirmed implementation
  • Documentation changes
  • Review current logging levels & increase trace/debug logging

The current state of the output window is not optimal. Highlighted from #25

Issue When the showOuputWindow setting is set to false the output isn’t optimised for errors. Plus some errors aren’t being shown (again, with the above setup)

Resolution See this comment

Old/outdated resolution
  • When the above setting is false the output only saves errors rather than the current full log.
  • All errors during compilation will also force the output to open, regardless of settings

When false, what exactly is going to be saved/shown?

Type Saved Shown
General error ✔️ ✔️
@error ✔️ ✔️
@warn ✔️
@debug ✔️
Autoprefixer warnings ✔️
Successful compilation
Start/Stop watching
Files found/compiling

Extension level errors will still show a pop out. Which you can still report using the liveSass.command.reportIssue command


This change also requires some document changed

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
glenn2223commented, Mar 22, 2021

@zigojacko, I’ll push your suggestion in the next alpha release

0reactions
glenn2223commented, Mar 25, 2021

Closed with v5.0.0-alpha.5 release

Read more comments on GitHub >

github_iconTop Results From Across the Web

Output Window, Debugging, Options Dialog Box
Find explanations, solutions, and workarounds for "Unable to set data breakpoint errors" that occur when using "Break when Value Changes". View ...
Read more >
Breaking Changes · microsoft/TypeScript Wiki - GitHub
These changes list where implementation differs between versions as the spec and compiler are simplified and inconsistencies are corrected. For ...
Read more >
"Show Output window when build starts" not working correctly
The Output window now opens for about 1/10 of a second, and then closes. It no longer remains open like it used too....
Read more >
visual studio 2012 - C# breaking changes - under the covers
Ive read the document from MS about the breaking changes in VS 2012 but Im trying to understand how this works under the...
Read more >
Version 2.x - Breaking Changes :: Documentation for Senzing
Platform Support Changes · MySQL 5.x and MariaDB 5.x support dropped · Windows 7 Limited Availability support dropped · macOS High Sierra Limited...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found