Skip to content

Instantly share code, notes, and snippets.

@orta

orta/tsc-compiler-errors-3.svg

Last active September 6, 2021 10:25
Show Gist options
  • Save orta/98a39ed57a3bb671a5e662c9401a6d5c to your computer and use it in GitHub Desktop.
Save orta/98a39ed57a3bb671a5e662c9401a6d5c to your computer and use it in GitHub Desktop.
Download ZIP
Ideas for TSC with prettier pretty settings - click raw on this svg below
Display the source blob
Display the rendered blob
Raw
tsc-compiler-errors-3.svg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@fbartho
Copy link

fbartho commented Aug 30, 2021 •
edited

This is frankly beautiful. It’s what I’ve seen demoed as peak compiler design in other languages, clear and helpful.

  1. How hard is this to deliver?
  2. Is this an unacceptable breaking change? (I hope not)
  3. Does this fall apart in skinny terminals? ~40cols

@orta
Copy link
Author

orta commented Aug 30, 2021 •
edited

👋

  1. How hard to deliver isn't really something we should worry about at design phase unless it's absolutely 'this isn't possible' - so far, I think it's generally possible
  2. Offhand this would affect the vscode/GitHub Actions error detection regexes for logs, but other than that I'd assume anyone who is parsing text output would not consider the text a stable output
  3. Nope, shouldn't do

@fbartho
Copy link

fbartho commented Aug 30, 2021

I love it! — Very constrained horizontal still looks good, but you’ve identified the challenges, and some hypothetical tricks.

Agreed with rest of comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment