Technology

Assertive Script consists of several components. This page provides some insights in the different software components that are involved when running Assertive Script.

High level architecture

The following diagram shows how the different components relate to eachother.

graph LR;

IDE["`IDE
_VSCode extension_`"]

Assertive.LanguageServer["`Assertive.LanguageServer
_.NET library_`"]

Assertive["`Assertive
_.NET library_`"]

Assertive.Cli["`Assertive.Cli
_.NET library_`"]

IDE <--> Assertive.LanguageServer
Assertive.LanguageServer --> Assertive
Assertive.Cli --> Assertive

Component	Description	Repository
Assertive	This is the core .NET assembly that contains the lexer, parser and interpreter. The parser and interpreter grammars are written in ANTLR. From these grammars, ANTLR is able to generate a C# visitor class. The interpreter and code analyser use subclasses of the visitor, in order to visit all statements and expressions. The Assertive library is written in pure C# and runs on .NET.	link
Assertive.Cli	The command line interface (CLI) to invoke the Assertive interpreter directly from a terminal. It has a direct dependency on the Assertive core library.	link
Assertive.LanguageServer	A language server protocol (LSP) implementation based on OmniSharp. This assembly has a direct depency on the Assertive core library. The component can be invoked by any language server client that knows the LSP protocol.	link
IDE (VSCode extension)	A language server client that runs on Node.js that invokes the Assertive.LanguageServer component. The Visual Studio Code extension code is written in TypeScript.	link