You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
js-slang first reads from tab files and then evaluates them
Frontend calls that raw tab to turn it into a ModuleSideContent
The idea of a "Tab" is entirely a frontend concept: thus I propose that we move the loading of module side content into the frontend. I think this would do us some good by continuing the separate the responsibilities between js-slang and the frontend.
The text was updated successfully, but these errors were encountered:
Right now there are two steps to tab loading:
js-slang
first reads from tab files and then evaluates themModuleSideContent
The idea of a "Tab" is entirely a frontend concept: thus I propose that we move the loading of module side content into the frontend. I think this would do us some good by continuing the separate the responsibilities between
js-slang
and the frontend.The text was updated successfully, but these errors were encountered: