API Graph in WebScript

February 2, 2018 by Igor Lozhkin
Typical APIs created with Arnica WebScript include multiple scripts within script (API) container. Individual scripts are usually specialized code blocks, written in different languages, which implement specific functionalities needed by the API. This include validation rules, SQL queries, business logic, emailing, HTML artifacts, CSS blocks, javascripts, etc. 

The following is an example of public API GenerateOrder in API container GenerateCustomerOrder:


The list shows script type (for example, public, local, constructor, destructor, etc.), its programming language and other properties. However, this list does not show dependencies. 

Top level dependency view (using and used by) may be accessed from the public API properties page:

Developers may switch to a full dependency analysis graph in both visual and textual forms:


API graphs let users drill-down any intermediate scripts within API container dependencies:

This article provides an example of how a script graph may be used to analyze dependencies.