We can use a new, advanced way to handle the language service by using the LSP protocol, but in this example, the language service and the editor will be in the same process, which is the browser, without any back-end processing. Language service, on the other hand, is responsible for parsing the code, generating the Abstract syntax tree(AST), finding any possible syntax or lexical errors, using the AST to find any semantic errors, formatting the code, etc.
This should happen asynchronously to have a good user experience. For example, when the user types some code and wants to format the code ( clicks Shift + Alt + F), the worker will receive a message containing the action “Format” and the code to be formatted. The worker itself will respond with a message containing the results. The other thread takes the changes the user made and does the heavy calculations, which includes code parsing and other compilation stuff.įor every change in the editor (it could be for every character the user typed or until the user stopped typing for 2 seconds), a message will be sent to the Language Service worker to do some actions. One is responsible for UI stuff, such as waiting for the user to type some code or do some actions. I’ll get back to these semantic rules later in this article.īefore we dig deep into the code, let’s start first with a general architecture of a web editor or any editor in general.Īs we can see from the above schema, in general, there are two threads in any editor. The COMPLETE instruction should not be applied in a TODO that has not been declared using ADD TODO.If a TODO is defined using the ADD TODO instruction, we can re-add it.Here are some semantics I’ll be using for semantic validation of TodoLang code: It will not support multiple file or code editing. Note: The editor will only support one code or file editing at once. We are going to make the editor support the following features: It may seem useless, but it has everything I need to cover in this article. This is a simple language I’ve invented for the purpose of this article. Or we can complete a TODO using COMPLETE TODO “todo_text” so that the output of interpreting this code can tell us about the remaining TODOs and the ones we have done so far. We simply add some TODOs using the following: ADD TODO "TODO_TEXT"
0 kommentar(er)
