Someone said we should make the view source searchable, and that we should show any errors on a view.
Actually, it might have been a few dozen of you.
A reader reminded me that we actually implemented this in v4.2.
I’ll go into more depth here next week when I’m back from Open World, but we’re working on building a new advanced Code Outline. Right click in your editor to open it.
It’s a bit too verbose now, but you can see how our parser SEES your code. This is how we know to highlight something, change it’s case, print syntax/grammar warnings BEFORE you try to run your code, and of course it’s how we know how to format your code.
It’s something that might involve into a sort of code diagram so you can visually see how your SQL and PL/SQL are setup.
There’s a toggle to switch back to the plain-jane outline if it’s too much for you to take in all at once now.