@eagleoutice/flowr 2.2.12 → 2.2.13

package/documentation/print-linting-and-testing-wiki.js

@@ -22,32 +22,34 @@ function getText() {
 For the latest code coverage information, see [codecov.io](${doc_files_1.FlowrCodecovRef}), 
 for the latest benchmark results, see the [benchmark results](${doc_files_1.FlowrSiteBaseRef}/wiki/stats/benchmark) wiki page.
 
-- [Testing Suites](#testing-suites)
-  - [Functionality Tests](#functionality-tests)
-    - [Test Structure](#test-structure)
-    - [Writing a Test](#writing-a-test)
-    - [Running Only Some Tests](#running-only-some-tests)
-  - [System Tests](#system-tests)
-  - [Performance Tests](#performance-tests)
-  - [Oh no, the tests are slow](#oh-no-the-tests-are-slow)
-  - [Testing Within Your IDE](#testing-within-your-ide)
+- [🏨 Testing Suites](#testing-suites)
+  - [🧪 Functionality Tests](#functionality-tests)
+    - [🏗️ Test Structure](#test-structure)
+    - [🏷️ Test Labels](#test-labels)
+    - [🖋️ Writing a Test](#writing-a-test)
+    - [🤏 Running Only Some Tests](#running-only-some-tests)
+  - [💽 System Tests](#system-tests)
+  - [💃 Performance Tests](#performance-tests)
+  - [📝 Testing Within Your IDE](#testing-within-your-ide)
     - [VS Code](#vs-code)
     - [Webstorm](#webstorm)
-- [CI Pipeline](#ci-pipeline)
-- [Linting](#linting)
+- [🪈 CI Pipeline](#ci-pipeline)
+- [🧹 Linting](#linting)
   - [Oh no, the linter fails](#oh-no-the-linter-fails)
   - [License Checker](#license-checker)
-- [Debugging](#debugging)
+- [🐛 Debugging](#debugging)
   - [VS Code](#vs-code-1)
 
-## Testing Suites
+<a id='testing-suites'></a>
+## 🏨 Testing Suites
 
 Currently, flowR contains three testing suites: one for [functionality](#functionality-tests), 
 one for [system tests](#system-tests), and one for [performance](#performance-tests). We explain each of them in the following.
 In addition to running those tests, you can use the more generalized \`npm run checkup\`. 
 This command includes the construction of the docker image, the generation of the wiki pages, and the linter.
 
-### Functionality Tests
+<a id='functionality-tests'></a>
+### 🧪 Functionality Tests
 
 The functionality tests represent conventional unit (and depending on your terminology component/api) tests.
 We use [vitest](https://vitest.dev/) as our testing framework.
@@ -75,7 +77,8 @@ some tests may be skipped automatically as they do not apply to your current sys
 Each test can specify such requirements as part of the \`TestConfiguration\`, which is then used in the \`test.skipIf\` function of _vitest_.
 It is up to the [ci](#ci-pipeline) to run the tests on different systems to ensure that those tests run.
 
-#### Test Structure
+<a id='test-structure'></a>
+#### 🏗️ Test Structure
 
 All functionality tests are to be located under [test/functionality](${doc_files_1.RemoteFlowrFilePathBaseRef}/test/functionality).
 
@@ -94,15 +97,24 @@ to disable parallel execution for the respective test (otherwise, such tests are
 `
     })}
 
-#### Writing a Test
+<a id='test-labels'></a>
+#### 🏷️ Test Labels
 
-Currently, this is heavily dependent on what you want to test (normalization, dataflow, quad-export, …) 
-and it is probably best to have a look at existing tests in that area to get an idea of what comfort functionality is available.
+Generally, tests are [labeled](${doc_files_1.RemoteFlowrFilePathBaseRef}test/functionality/_helper/label.ts) according to the *flowR* capabilities they test. 
 
-Generally, tests should be [labeled](${doc_files_1.RemoteFlowrFilePathBaseRef}test/functionality/_helper/label.ts) according to the *flowR* capabilities they test. 
 The set of currently supported capabilities and their IDs can be found in ${(0, doc_files_1.getFilePathMd)('../r-bridge/data/data.ts')}. 
+
 The resulting labels are used in the test report that is generated as part of the test output. 
 They group tests by the capabilities they test and allow the report to display how many tests ensure that any given capability is properly supported.
+The report can be found on the wiki's [capabilities page](${doc_files_1.FlowrWikiBaseRef}/Capabilities).
+
+To add new labels, simply add them to the relevant section in ${(0, doc_files_1.getFilePathMd)('../r-bridge/data/data.ts')} as part of a pull request.
+
+<a id='writing-a-test'></a>
+#### 🖋️ Writing a Test
+
+Currently, this is heavily dependent on what you want to test (normalization, dataflow, quad-export, …) 
+and it is probably best to have a look at existing tests in that area to get an idea of what comfort functionality is available.
 
 Various helper functions are available to ease in writing tests with common behaviors, like testing for dataflow, slicing or query results. 
 These can be found in [the \`_helper\` subdirectory](${doc_files_1.RemoteFlowrFilePathBaseRef}test/functionality/_helper).
@@ -136,12 +148,14 @@ assertDataflow(label('without distractors', [...OperatorDatabase['<-'].capabilit
 );
 `)}
 
-#### Running Only Some Tests
+<a id='running-only-some-tests'></a>
+#### 🤏 Running Only Some Tests
 
 To run only some tests, vitest allows you to [filter](https://vitest.dev/guide/filtering.html) tests. 
 Besides, you can use the watch mode (with \`npm run test\`) to only run tests that are affected by your changes.
 
-### System Tests
+<a id='system-tests'></a>
+### 💽 System Tests
 
 In contrast to the [functionality tests](#functionality-tests), the system tests use runners like the \`npm\` scripts
 to test the behavior of the whole system, for example, by running the CLI or the server.
@@ -154,9 +168,8 @@ with the [functionality tests](#functionality-tests)).
 
 Have a look at the [test/system-tests](${doc_files_1.RemoteFlowrFilePathBaseRef}test/system-tests) folder for more information.
  
-
-
-### Performance Tests
+<a id='performance-tests'></a>
+### 💃 Performance Tests
 
 The performance test suite of *flowR* uses several suites to check for variations in the required times for certain steps.
 Although we measure wall time in the CI (which is subject to rather large variations), it should give a rough idea *flowR*'s performance.
@@ -167,8 +180,8 @@ ${(0, doc_code_1.codeBlock)('shell', 'npm run performance-test')}
 
 See [test/performance](${doc_files_1.RemoteFlowrFilePathBaseRef}test/performance) for more information on the suites, how to run them, and their results. If you are interested in the results of the benchmarks, see [here](${doc_files_1.FlowrSiteBaseRef}/wiki/stats/benchmark).
 
-
-### Testing Within Your IDE
+<a id='testing-within-your-ide'></a>
+### 📝 Testing Within Your IDE
 
 #### VS Code
 
@@ -188,8 +201,8 @@ To get started, install the [vitest Extension](https://marketplace.visualstudio.
 
 Please follow the official guide [here](https://www.jetbrains.com/help/webstorm/vitest.html).
 
-
-## CI Pipeline
+<a id='ci-pipeline'></a>
+## 🪈 CI Pipeline
 
 We have several workflows defined in [.github/workflows](${doc_files_1.RemoteFlowrFilePathBaseRef}/.github/workflows/).
 We explain the most important workflows in the following:
@@ -203,8 +216,9 @@ We explain the most important workflows in the following:
   - deploying the documentation to [GitHub Pages](${doc_files_1.FlowrSiteBaseRef}/doc/)
 - [release.yaml](${doc_files_1.RemoteFlowrFilePathBaseRef}/.github/workflows/release.yaml) is responsible for creating a new release, only to be run by repository owners. Furthermore, it adds the new docker image to [docker hub](${doc_files_1.FlowrDockerRef}).
 - [broken-links-and-wiki.yaml](${doc_files_1.RemoteFlowrFilePathBaseRef}/.github/workflows/broken-links-and-wiki.yaml) repeatedly tests that all links are not dead!
-
-## Linting
+ 
+<a id='linting'></a>
+## 🧹 Linting
 
 There are two linting scripts.
 The main one:
@@ -222,21 +236,23 @@ eslint can automatically fix several linting problems[](https://eslint.org/docs/
 So you may be fine by just running:
 
 ${(0, doc_code_1.codeBlock)('shell', 'npm run lint-local -- --fix')}
-
-### Oh no, the linter fails
+ 
+<a id='oh-no-the-linter-fails'></a>
+### 💥 Oh no, the linter fails
 
 By now, the rules should be rather stable and so, if the linter fails,
 it is usually best if you (when necessary) read the respective description and fix the respective problem.
 Rules in this project cover general JavaScript issues [using regular ESLint](https://eslint.org/docs/latest/rules), TypeScript-specific issues [using typescript-eslint](https://typescript-eslint.io/rules/), and code formatting [with ESLint Stylistic](https://eslint.style/packages/default#rules).
 
 However, in case you think that the linter is wrong, please do not hesitate to open a [new issue](${doc_files_1.FlowrGithubBaseRef}/flowr/issues/new/choose).
-
-### License Checker
+ 
+<a id='license-checker'></a>
+### 🪪 License Checker
 
 *flowR* is licensed under the [GPLv3 License](${doc_files_1.FlowrGithubBaseRef}/flowr/blob/main/LICENSE) requiring us to only rely on [compatible licenses](https://www.gnu.org/licenses/license-list.en.html). For now, this list is hardcoded as part of the npm [\`license-compat\`](${doc_files_1.RemoteFlowrFilePathBaseRef}/package.json) script so it can very well be that a new dependency you add causes the checker to fail &mdash; *even though it is compatible*. In that case, please either open a [new issue](${doc_files_1.FlowrGithubBaseRef}/flowr/issues/new/choose) or directly add the license to the list (including a reference to why it is compatible).
 
-
-## Debugging
+<a id='debugging'></a>
+## 🐛 Debugging
 ### VS Code
 When working with VS Code, you can attach a debugger to the REPL. This works automatically by running the \`Start Debugging\` command (\`F5\` by default).
 You can also set the \`Auto Attach Filter\` setting to automatically attach the debugger, when running \`npm run flowr\`.

package/documentation/print-normalized-ast-wiki.js

@@ -12,7 +12,7 @@ const doc_types_1 = require("./doc-util/doc-types");
 const path_1 = __importDefault(require("path"));
 const doc_files_1 = require("./doc-util/doc-files");
 const doc_cli_option_1 = require("./doc-util/doc-cli-option");
-const time_1 = require("../util/time");
+const time_1 = require("../util/text/time");
 const doc_structure_1 = require("./doc-util/doc-structure");
 const pipeline_executor_1 = require("../core/pipeline-executor");
 const retriever_1 = require("../r-bridge/retriever");

package/documentation/print-onboarding-wiki.d.ts

@@ -0,0 +1 @@
+export {};

package/documentation/print-onboarding-wiki.js

@@ -0,0 +1,42 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+const log_1 = require("../../test/functionality/_helper/log");
+const doc_files_1 = require("./doc-util/doc-files");
+const doc_code_1 = require("./doc-util/doc-code");
+const doc_auto_gen_1 = require("./doc-util/doc-auto-gen");
+function print() {
+    return `${(0, doc_auto_gen_1.autoGenHeader)({ filename: module.filename, purpose: 'developer onboarding process' })}	
+	
+To get started developing on *flowR*, we recommend carefully reading the following pages:
+- 💻 [Setting up the *flowR* development environment](${doc_files_1.FlowrWikiBaseRef}/Setup#%EF%B8%8F-building-from-scratch).\
+  This page explains how to install **R** and **Node.js**.  
+- 💖 [Contributing guidelines](${doc_files_1.FlowrGithubBaseRef}/flowr/tree/main/.github/CONTRIBUTING.md).\
+  This page also includes information about how to set up **git-lfs** and several **git hooks**.
+
+## ⌛ TL;DR
+
+The most important steps to get the *flowR* development environment set up (after installing **R** and **Node.js**) can be seen below. For convenience, they can be executed all at once using the following command:
+${(0, doc_code_1.codeBlock)('shell', 'npm run setup:dev')}
+
+If you want to execute the steps manually, please follow the instructions below:
+
+${(0, doc_code_1.codeBlock)('shell', `
+# Installing git-lfs for your current user (if you haven't already)
+git lfs install
+# Cloning the repository
+git clone https://github.com/flowr-analysis/flowr.git
+# Installing dependencies
+npm ci
+# Configuring git hooks
+git config --local core.hooksPath .githooks/
+# Test if the git hooks are working correctly
+# Running this command should lint the code
+git push --dry-run
+`)}
+    `.trim();
+}
+if (require.main === module) {
+    (0, log_1.setMinLevelOfAllLogs)(6 /* LogLevel.Fatal */);
+    console.log(print());
+}
+//# sourceMappingURL=print-onboarding-wiki.js.map

package/documentation/print-query-wiki.js

@@ -10,7 +10,7 @@ const query_1 = require("../queries/query");
 const doc_files_1 = require("./doc-util/doc-files");
 const doc_query_1 = require("./doc-util/doc-query");
 const schema_1 = require("../util/schema");
-const ansi_1 = require("../util/ansi");
+const ansi_1 = require("../util/text/ansi");
 const call_context_query_executor_1 = require("../queries/catalog/call-context-query/call-context-query-executor");
 const compound_query_1 = require("../queries/virtual-query/compound-query");
 const doc_auto_gen_1 = require("./doc-util/doc-auto-gen");
@@ -238,6 +238,26 @@ ${await (0, doc_query_1.showQuery)(shell, exampleCode, [{
 		`;
     }
 });
+(0, doc_query_1.registerQueryDocumentation)('origin', {
+    name: 'Origin Query',
+    type: 'active',
+    shortDescription: 'Retrieve the origin of a variable, function call, ...',
+    functionName: search_query_executor_1.executeSearch.name,
+    functionFile: '../queries/catalog/origin-query/origin-query-executor.ts',
+    buildExplanation: async (shell) => {
+        const exampleCode = 'x <- 1\nprint(x)';
+        return `
+With this query you can use flowR's origin tracking to find out the read origins of a variable,
+the functions called by a call, and more.
+
+Using the example code \`${exampleCode}\` (with the \`print(x)\` in the second line), the following query returns the origins of \`x\` in the code:
+${await (0, doc_query_1.showQuery)(shell, exampleCode, [{
+                type: 'origin',
+                criterion: '2@x'
+            }], { showCode: true })}
+		`;
+    }
+});
 (0, doc_query_1.registerQueryDocumentation)('search', {
     name: 'Search Query',
     type: 'active',

package/documentation/print-readme.js

@@ -23,9 +23,12 @@ async function getText(shell) {
 [![Docker Image Version (latest semver)](https://img.shields.io/docker/v/eagleoutice/flowr?logo=docker&logoColor=white&label=dockerhub)](${doc_files_1.FlowrDockerRef})
 [![latest tag](https://badgen.net/github/tag/flowr-analysis/flowr?label=latest&color=purple)](${doc_files_1.FlowrGithubBaseRef}/flowr/releases/latest)
 [![Marketplace](https://badgen.net/vs-marketplace/v/code-inspect.vscode-flowr)](${doc_files_1.FlowrVsCode})
+[![Marketplace](https://badgen.net/open-vsx/version/code-inspect/vscode-flowr?label=Positron/Open%20VSX)](${doc_files_1.FlowrPositron})
 [![DOI](https://zenodo.org/badge/624819038.svg)](https://zenodo.org/doi/10.5281/zenodo.13319290)
 
-_flowR_ is a sophisticated, static [dataflow analyzer](https://en.wikipedia.org/wiki/Data-flow_analysis) for the [R programming language](https://www.r-project.org/).
+_flowR_ is a sophisticated, static [dataflow analyzer](https://en.wikipedia.org/wiki/Data-flow_analysis) for the [R programming language](https://www.r-project.org/),
+available for [VSCode](${doc_files_1.FlowrVsCode}), [Positron](${doc_files_1.FlowrPositron}), [RStudio](${doc_files_1.FlowrGithubBaseRef}/rstudio-addin-flowr),
+and [Docker](${doc_files_1.FlowrDockerRef}).
 It offers a wide variety of features, for example:
 
 * 🍕 **program slicing**\\
@@ -90,12 +93,16 @@ ${await (0, doc_dfg_1.printDfGraphForCode)(shell, (0, doc_files_1.getFileContent
 
 If you want to use flowR and the features it provides, feel free to check out the:
 
-- [Visual Studio Code extension](${doc_files_1.FlowrVsCode}): provides access to flowR directly in VS Code (or [vscode.dev](https://vscode.dev/))
+- [Visual Studio Code](${doc_files_1.FlowrVsCode})/[Positron](${doc_files_1.FlowrPositron}): provides access to flowR directly in VS Code and Positron (or [vscode.dev](https://vscode.dev/))
 - [RStudio Addin](${doc_files_1.FlowrGithubBaseRef}/rstudio-addin-flowr): integrates flowR into [RStudio](https://posit.co/downloads/)
 - [R package](${doc_files_1.FlowrGithubBaseRef}/flowr-r-adapter): use flowR in your R scripts
 - [Docker image](${doc_files_1.FlowrDockerRef}): run flowR in a container, this also includes [flowR's server](${doc_files_1.FlowrWikiBaseRef}/Interface#communicating-with-the-server)
 - [NPM package](${doc_files_1.FlowrNpmRef}): include flowR in your TypeScript and JavaScript projects
  
+
+If you are already using flowR and want to give feedback, please consider filling out our [feedback form](https://docs.google.com/forms/d/e/1FAIpQLScKFhgnh9LGVU7QzqLvFwZe1oiv_5jNhkIO-G-zND0ppqsMxQ/viewform).
+
+ 
 ## ⭐ Getting Started
 
 To get started with _flowR_ and its features, please check out the [Overview](${doc_files_1.FlowrGithubBaseRef}/flowr/wiki/Overview) wiki page. 
@@ -121,7 +128,7 @@ as well as the deployed [code documentation](https://flowr-analysis.github.io/fl
 
 ## 🚀 Contributing
 
-We welcome every contribution! Please check out the [contributing guidelines](${doc_files_1.FlowrGithubBaseRef}/flowr/tree/main/.github/CONTRIBUTING.md) for more information.
+We welcome every contribution! Please check out the [developer onboarding](${doc_files_1.FlowrWikiBaseRef}/Onboarding) section in the wiki for all the information you will need.
 
 ### Contributors
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eagleoutice/flowr",
-  "version": "2.2.12",
+  "version": "2.2.13",
   "description": "Static Dataflow Analyzer and Program Slicer for the R Programming Language",
   "types": "dist/src/index.d.ts",
   "repository": {
@@ -12,6 +12,7 @@
     "url": "https://github.com/flowr-analysis/flowr/issues"
   },
   "scripts": {
+    "setup:dev": "git lfs fetch && npm ci && git config --local core.hooksPath .githooks/ && git push --dry-run",
     "main": "npm run build:bundle-flowr && node dist/src/cli/flowr.min.js",
     "flowr": "npm run main --",
     "main-dev": "ts-node src/cli/flowr.ts",
@@ -33,13 +34,14 @@
     "wiki:search-api": "ts-node src/documentation/print-search-wiki.ts",
     "wiki:linting-and-testing": "ts-node src/documentation/print-linting-and-testing-wiki.ts",
     "wiki:interface": "ts-node src/documentation/print-interface-wiki.ts",
+    "wiki:onboarding": "ts-node src/documentation/print-onboarding-wiki.ts",
+    "wiki:faq": "ts-node src/documentation/print-faq-wiki.ts",
     "wiki:cfg": "ts-node src/documentation/print-cfg-wiki.ts",
     "gen:readme": "ts-node src/documentation/print-readme.ts",
     "build": "tsc --project .",
     "build-dev": "npm run build && npm run build:copy-wasm",
-    "build:bundle-flowr": "npm run build && esbuild --bundle dist/src/cli/flowr.js --platform=node --tree-shaking=true --bundle --minify --external:clipboardy --target=node22 --outfile=dist/src/cli/flowr.min.js && npm run build:copy-wasm-min",
-    "build:copy-wasm": "mkdir -p dist/src/r-bridge/lang-4.x/tree-sitter/ && cp src/r-bridge/lang-4.x/tree-sitter/tree-sitter-r.wasm src/r-bridge/lang-4.x/tree-sitter/tree-sitter.wasm dist/src/r-bridge/lang-4.x/tree-sitter/",
-    "build:copy-wasm-min": "mkdir -p dist/src/cli && cp src/r-bridge/lang-4.x/tree-sitter/tree-sitter-r.wasm src/r-bridge/lang-4.x/tree-sitter/tree-sitter.wasm dist/src/cli",
+    "build:bundle-flowr": "npm run build && esbuild --bundle dist/src/cli/flowr.js --platform=node --tree-shaking=true --bundle --minify --external:clipboardy --target=node22 --outfile=dist/src/cli/flowr.min.js && npm run build:copy-wasm",
+    "build:copy-wasm": "mkdir -p dist/node_modules/@eagleoutice/tree-sitter-r/ && mkdir -p dist/node_modules/web-tree-sitter && cp node_modules/@eagleoutice/tree-sitter-r/tree-sitter-r.wasm dist/node_modules/@eagleoutice/tree-sitter-r/  && cp node_modules/web-tree-sitter/tree-sitter.wasm dist/node_modules/web-tree-sitter/",
     "lint-local": "npx eslint --version && npx eslint src/ test/ --rule \"no-warning-comments: off\"",
     "lint": "npm run license-compat -- --summary && npx eslint --version && npx eslint src/ test/",
     "license-compat": "license-checker --onlyAllow 'MIT;MIT OR X11;GPLv2;LGPL;GNUGPL;ISC;Apache-2.0;FreeBSD;BSD-2-Clause;clearbsd;ModifiedBSD;BSD-3-Clause;Python-2.0;Unlicense;WTFPL;BlueOak-1.0.0;CC-BY-4.0;CC-BY-3.0;CC0-1.0;0BSD'",
@@ -175,7 +177,7 @@
     "@eagleoutice/eslint-config-flowr": "^1.0.17",
     "@eslint/eslintrc": "^3.2.0",
     "@eslint/js": "^9.20.0",
-    "@j-ulrich/release-it-regex-bumper": "^5.2.0",
+    "@j-ulrich/release-it-regex-bumper": "^5.3.0",
     "@types/command-line-args": "^5.2.3",
     "@types/command-line-usage": "^5.0.4",
     "@types/n-readlines": "^1.0.6",
@@ -190,7 +192,7 @@
     "eslint": "^9.20.1",
     "license-checker": "^25.0.1",
     "npm-run-all": "^4.1.5",
-    "release-it": "^18.1.2",
+    "release-it": "^19.0.2",
     "ts-node": "^10.9.2",
     "typedoc": "^0.27.7",
     "typedoc-plugin-missing-exports": "^3.1.0",
@@ -200,6 +202,7 @@
     "vitest": "^3.0.6"
   },
   "dependencies": {
+    "@eagleoutice/tree-sitter-r": "^1.1.2",
     "@xmldom/xmldom": "^0.9.7",
     "clipboardy": "^4.0.0",
     "command-line-args": "^6.0.1",

package/queries/catalog/call-context-query/call-context-query-executor.js

@@ -4,7 +4,7 @@ exports.executeCallContextQueries = executeCallContextQueries;
 const node_id_1 = require("../../../r-bridge/lang-4.x/ast/model/processing/node-id");
 const vertex_1 = require("../../../dataflow/graph/vertex");
 const edge_1 = require("../../../dataflow/graph/edge");
-const cfg_1 = require("../../../util/cfg/cfg");
+const extract_cfg_1 = require("../../../control-flow/extract-cfg");
 const two_layer_collector_1 = require("../../two-layer-collector");
 const objects_1 = require("../../../util/objects");
 const identify_link_to_last_call_relation_1 = require("./identify-link-to-last-call-relation");
@@ -85,7 +85,7 @@ function retrieveAllCallAliases(nodeId, graph) {
     const aliases = new Map();
     const visited = new Set();
     /* we store the current call name */
-    const queue = [[(0, node_id_1.recoverContent)(nodeId, graph) ?? '', nodeId]];
+    let queue = [[(0, node_id_1.recoverContent)(nodeId, graph) ?? '', nodeId]];
     while (queue.length > 0) {
         const [str, id] = queue.shift();
         if (visited.has(id)) {
@@ -111,7 +111,7 @@ function retrieveAllCallAliases(nodeId, graph) {
                 .filter(([, { types }]) => (0, edge_1.edgeIncludesType)(types, edge_1.EdgeType.Reads | edge_1.EdgeType.DefinedBy | edge_1.EdgeType.DefinedByOnCall))
                 .map(([t]) => [(0, node_id_1.recoverContent)(t, graph) ?? '', t]);
             /** only follow defined-by and reads */
-            queue.push(...x);
+            queue = queue.concat(x);
             continue;
         }
         let track = edge_1.EdgeType.Calls | edge_1.EdgeType.Reads | edge_1.EdgeType.DefinedBy | edge_1.EdgeType.DefinedByOnCall;
@@ -180,7 +180,7 @@ function executeCallContextQueries({ dataflow: { graph }, ast }, queries) {
     const { promotedQueries, requiresCfg } = promoteQueryCallNames(queries);
     let cfg = undefined;
     if (requiresCfg) {
-        cfg = (0, cfg_1.extractCFG)(ast, graph);
+        cfg = (0, extract_cfg_1.extractCFG)(ast, graph, []);
     }
     const queriesWhichWantAliases = promotedQueries.filter(q => q.includeAliases);
     for (const [nodeId, info] of graph.vertices(true)) {
@@ -203,7 +203,7 @@ function executeCallContextQueries({ dataflow: { graph }, ast }, queries) {
                 }
             }
         }
-        for (const query of promotedQueries.filter(q => q.callName.test(info.name))) {
+        for (const query of promotedQueries.filter(q => !q.includeAliases && q.callName.test(info.name))) {
             const file = ast.idMap.get(nodeId)?.info.file;
             if (!doesFilepathMatch(file, query.fileFilter)) {
                 continue;

package/queries/catalog/call-context-query/call-context-query-format.d.ts

@@ -1,7 +1,7 @@
 import type { BaseQueryFormat, BaseQueryResult } from '../../base-query-format';
 import type { NodeId } from '../../../r-bridge/lang-4.x/ast/model/processing/node-id';
 import { executeCallContextQueries } from './call-context-query-executor';
-import type { OutputFormatter } from '../../../util/ansi';
+import type { OutputFormatter } from '../../../util/text/ansi';
 import Joi from 'joi';
 import type { PipelineOutput } from '../../../core/steps/pipeline/pipeline';
 import type { DEFAULT_DATAFLOW_PIPELINE } from '../../../core/steps/pipeline/default-pipelines';

package/queries/catalog/call-context-query/call-context-query-format.js

@@ -5,8 +5,8 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.CallContextQueryDefinition = void 0;
 const call_context_query_executor_1 = require("./call-context-query-executor");
-const ansi_1 = require("../../../util/ansi");
-const time_1 = require("../../../util/time");
+const ansi_1 = require("../../../util/text/ansi");
+const time_1 = require("../../../util/text/time");
 const joi_1 = __importDefault(require("joi"));
 const query_print_1 = require("../../query-print");
 const identify_link_to_last_call_relation_1 = require("./identify-link-to-last-call-relation");

package/queries/catalog/call-context-query/identify-link-to-last-call-relation.d.ts

@@ -1,12 +1,12 @@
 import type { NodeId } from '../../../r-bridge/lang-4.x/ast/model/processing/node-id';
-import type { ControlFlowGraph } from '../../../util/cfg/cfg';
 import type { DataflowGraph } from '../../../dataflow/graph/graph';
 import type { DataflowGraphVertexFunctionCall } from '../../../dataflow/graph/vertex';
 import { RType } from '../../../r-bridge/lang-4.x/ast/model/type';
 import type { RNodeWithParent } from '../../../r-bridge/lang-4.x/ast/model/processing/decorate';
 import type { LinkTo } from './call-context-query-format';
+import type { ControlFlowGraph } from '../../../control-flow/control-flow-graph';
 export declare enum CallTargets {
-    /** call targets a function that is not defined locally (e.g., the call targets a library function) */
+    /** call targets a function that is not defined locally in the script (e.g., the call targets a library function) */
     OnlyGlobal = "global",
     /** call targets a function that is defined locally or globally, but must include a global function */
     MustIncludeGlobal = "must-include-global",

package/queries/catalog/call-context-query/identify-link-to-last-call-relation.js

@@ -5,7 +5,7 @@ exports.satisfiesCallTargets = satisfiesCallTargets;
 exports.getValueOfArgument = getValueOfArgument;
 exports.identifyLinkToLastCallRelation = identifyLinkToLastCallRelation;
 const graph_1 = require("../../../dataflow/graph/graph");
-const visitor_1 = require("../../../util/cfg/visitor");
+const simple_visitor_1 = require("../../../control-flow/simple-visitor");
 const vertex_1 = require("../../../dataflow/graph/vertex");
 const edge_1 = require("../../../dataflow/graph/edge");
 const resolve_by_name_1 = require("../../../dataflow/environments/resolve-by-name");
@@ -17,7 +17,7 @@ const r_function_call_1 = require("../../../r-bridge/lang-4.x/ast/model/nodes/r-
 const cascade_action_1 = require("./cascade-action");
 var CallTargets;
 (function (CallTargets) {
-    /** call targets a function that is not defined locally (e.g., the call targets a library function) */
+    /** call targets a function that is not defined locally in the script (e.g., the call targets a library function) */
     CallTargets["OnlyGlobal"] = "global";
     /** call targets a function that is defined locally or globally, but must include a global function */
     CallTargets["MustIncludeGlobal"] = "must-include-global";
@@ -29,16 +29,19 @@ var CallTargets;
     CallTargets["Any"] = "any";
 })(CallTargets || (exports.CallTargets = CallTargets = {}));
 function satisfiesCallTargets(id, graph, callTarget) {
-    const callVertex = graph.get(id);
-    if (callVertex === undefined || callVertex[0].tag !== vertex_1.VertexType.FunctionCall) {
+    const callVertex = graph.getVertex(id, true);
+    if (callVertex === undefined || callVertex.tag !== vertex_1.VertexType.FunctionCall) {
+        return 'no';
+    }
+    const outgoing = graph.outgoingEdges(id);
+    if (outgoing === undefined) {
         return 'no';
     }
-    const [info, outgoing] = callVertex;
     const callTargets = [...outgoing]
-        .filter(([, e]) => (0, edge_1.edgeIncludesType)(e.types, edge_1.EdgeType.Calls))
+        .filter(([, { types }]) => (0, edge_1.edgeIncludesType)(types, edge_1.EdgeType.Calls))
         .map(([t]) => t);
     let builtIn = false;
-    if (info.environment === undefined) {
+    if (callVertex.environment === undefined) {
         /* if we have a call with an unbound environment,
          * this only happens if we are sure of built-in relations and want to save references
          */
@@ -49,8 +52,8 @@ function satisfiesCallTargets(id, graph, callTarget) {
          * for performance and scoping reasons, flowR will not identify the global linkage,
          * including any potential built-in mapping.
          */
-        const reResolved = (0, resolve_by_name_1.resolveByName)(info.name, info.environment, identifier_1.ReferenceType.Unknown);
-        if (reResolved?.some(t => t.definedAt === built_in_1.BuiltIn)) {
+        const reResolved = (0, resolve_by_name_1.resolveByName)(callVertex.name, callVertex.environment, identifier_1.ReferenceType.Unknown);
+        if (reResolved?.some(t => (0, built_in_1.isBuiltIn)(t.definedAt))) {
             builtIn = true;
         }
     }
@@ -58,19 +61,19 @@ function satisfiesCallTargets(id, graph, callTarget) {
         case CallTargets.Any:
             return callTargets;
         case CallTargets.OnlyGlobal:
-            if (callTargets.length === 0) {
-                return builtIn ? [built_in_1.BuiltIn] : [];
+            if (callTargets.every(built_in_1.isBuiltIn)) {
+                return builtIn ? ['built-in'] : [];
             }
             else {
                 return 'no';
             }
         case CallTargets.MustIncludeGlobal:
-            return builtIn || callTargets.length === 0 ? [...callTargets, built_in_1.BuiltIn] : 'no';
+            return builtIn || callTargets.length === 0 ? [...callTargets, 'built-in'] : 'no';
         case CallTargets.OnlyLocal:
             return !builtIn && callTargets.length > 0 ? callTargets : 'no';
         case CallTargets.MustIncludeLocal:
             if (callTargets.length > 0) {
-                return builtIn ? [...callTargets, built_in_1.BuiltIn] : callTargets;
+                return builtIn ? [...callTargets, 'built-in'] : callTargets;
             }
             else {
                 return 'no';
@@ -105,25 +108,25 @@ function getValueOfArgument(graph, call, argument, additionalAllowedTypes) {
     }
 }
 function identifyLinkToLastCallRelation(from, cfg, graph, { callName, ignoreIf, cascadeIf }) {
-    const found = [];
     if (ignoreIf && ignoreIf(from, graph)) {
-        return found;
+        return [];
     }
-    (0, visitor_1.visitCfgInReverseOrder)(cfg, from, node => {
+    const found = [];
+    (0, simple_visitor_1.visitCfgInReverseOrder)(cfg, [from], node => {
         /* we ignore the start id as it cannot be the last call */
         if (node === from) {
             return;
         }
-        const vertex = graph.get(node);
-        if (vertex === undefined || vertex[0].tag !== vertex_1.VertexType.FunctionCall) {
+        const vertex = graph.getVertex(node, true);
+        if (vertex === undefined || vertex.tag !== vertex_1.VertexType.FunctionCall) {
             return;
         }
-        if (callName.test(vertex[0].name)) {
-            const act = cascadeIf ? cascadeIf(vertex[0], from, graph) : cascade_action_1.CascadeAction.Stop;
+        if (callName.test(vertex.name)) {
+            const act = cascadeIf ? cascadeIf(vertex, from, graph) : cascade_action_1.CascadeAction.Stop;
             if (act === cascade_action_1.CascadeAction.Skip) {
                 return;
             }
-            const tar = satisfiesCallTargets(vertex[0].id, graph, CallTargets.MustIncludeGlobal);
+            const tar = satisfiesCallTargets(vertex.id, graph, CallTargets.MustIncludeGlobal);
             if (tar === 'no') {
                 return act === cascade_action_1.CascadeAction.Stop;
             }

package/queries/catalog/cluster-query/cluster-query-format.d.ts

@@ -14,7 +14,7 @@ export interface DataflowClusterQueryResult extends BaseQueryResult {
 }
 export declare const ClusterQueryDefinition: {
     readonly executor: typeof executeDataflowClusterQuery;
-    readonly asciiSummarizer: (formatter: import("../../../util/ansi").OutputFormatter, processed: import("../../../core/steps/pipeline/pipeline").PipelineOutput<import("../../../core/steps/pipeline/pipeline").Pipeline<{
+    readonly asciiSummarizer: (formatter: import("../../../util/text/ansi").OutputFormatter, processed: import("../../../core/steps/pipeline/pipeline").PipelineOutput<import("../../../core/steps/pipeline/pipeline").Pipeline<{
         readonly name: "parse";
         readonly humanReadableName: "parse with R shell";
         readonly description: "Parse the given R code into an AST";

package/queries/catalog/cluster-query/cluster-query-format.js

@@ -4,7 +4,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 };
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ClusterQueryDefinition = void 0;
-const ansi_1 = require("../../../util/ansi");
+const ansi_1 = require("../../../util/text/ansi");
 const joi_1 = __importDefault(require("joi"));
 const cluster_query_executor_1 = require("./cluster-query-executor");
 const dfg_1 = require("../../../util/mermaid/dfg");

package/queries/catalog/config-query/config-query-format.d.ts

@@ -1,6 +1,6 @@
 import type { BaseQueryFormat, BaseQueryResult } from '../../base-query-format';
 import { executeConfigQuery } from './config-query-executor';
-import { type OutputFormatter } from '../../../util/ansi';
+import { type OutputFormatter } from '../../../util/text/ansi';
 import Joi from 'joi';
 import type { FlowrConfigOptions } from '../../../config';
 export interface ConfigQuery extends BaseQueryFormat {

package/queries/catalog/config-query/config-query-format.js

@@ -5,8 +5,8 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ConfigQueryDefinition = void 0;
 const config_query_executor_1 = require("./config-query-executor");
-const ansi_1 = require("../../../util/ansi");
-const time_1 = require("../../../util/time");
+const ansi_1 = require("../../../util/text/ansi");
+const time_1 = require("../../../util/text/time");
 const joi_1 = __importDefault(require("joi"));
 const json_1 = require("../../../util/json");
 exports.ConfigQueryDefinition = {

package/queries/catalog/dataflow-lens-query/dataflow-lens-query-format.d.ts

@@ -14,7 +14,7 @@ export interface DataflowLensQueryResult extends BaseQueryResult {
 }
 export declare const DataflowLensQueryDefinition: {
     readonly executor: typeof executeDataflowLensQuery;
-    readonly asciiSummarizer: (formatter: import("../../../util/ansi").OutputFormatter, _processed: import("../../../core/steps/pipeline/pipeline").PipelineOutput<import("../../../core/steps/pipeline/pipeline").Pipeline<{
+    readonly asciiSummarizer: (formatter: import("../../../util/text/ansi").OutputFormatter, _processed: import("../../../core/steps/pipeline/pipeline").PipelineOutput<import("../../../core/steps/pipeline/pipeline").Pipeline<{
         readonly name: "parse";
         readonly humanReadableName: "parse with R shell";
         readonly description: "Parse the given R code into an AST";