I added a type-checker feature description. As I suspected, once a person turns on the type-checker, they stay in that mode for all the other tabs as well.
But that exposes errors in some of the other tabs. Not sure what to do about that in general. For instance, the Examples tab now gives an error because all functions need annotations. Tables of course still cause an internal error (can we not at least give a more graceful error?).
Notably, right now, when you go to External Data, there's a big, ugly error saying open-table is not found.
Given that it is basically impossible to write everything in a typed way, is there a way to not cause this modal to persist? Otherwise maybe types should become the last entry, which is not where I want to put them, but also, no matter where we put it, some people may beeline for it before trying everything else.
I added a type-checker feature description. As I suspected, once a person turns on the type-checker, they stay in that mode for all the other tabs as well.
But that exposes errors in some of the other tabs. Not sure what to do about that in general. For instance, the Examples tab now gives an error because all functions need annotations. Tables of course still cause an internal error (can we not at least give a more graceful error?).
Notably, right now, when you go to External Data, there's a big, ugly error saying
open-tableis not found.Given that it is basically impossible to write everything in a typed way, is there a way to not cause this modal to persist? Otherwise maybe types should become the last entry, which is not where I want to put them, but also, no matter where we put it, some people may beeline for it before trying everything else.