ReadonlyabstractReadonlydataFrame: {The configuration of the shape inference for data frames
ReadonlymaxColNames: numberThe maximum number of columns names to infer for data frames before over-approximating the column names to top
ReadonlyreadLoadedData: { maxReadLines: number; readExternalFiles: boolean }Configuration options for reading data frame shapes from loaded external data files, such as CSV files
ReadonlymaxReadLines: numberThe maximum number of lines to read when extracting data frame shapes from loaded files, such as CSV files
ReadonlyreadExternalFiles: booleanWhether data frame shapes should be extracted from loaded external data files, such as CSV files
ReadonlywideningThreshold: numberThe threshold for the number of visitations of a node at which widening should be performed to ensure the termination of the fixpoint iteration
Optional ReadonlydefaultThe default engine to use for interacting with R code. If this is undefined, an arbitrary engine from engines will be used.
ReadonlyenginesThe engines to use for interacting with R code. Currently, supports TreeSitterEngineConfig and RShellEngineConfig. An empty array means all available engines will be used.
ReadonlyignoreWhether source calls should be ignored, causing processSourceCall's behavior to be skipped
ReadonlyprojectWhether to resolve unknown paths loaded by the r project disk when trying to source/analyze files
ReadonlyreplConfiguration options for the REPL
This instruments the dataflow processors to count how often each processor is called
Whether to show quick stats in the REPL after each evaluation
ReadonlysemanticsConfigure language semantics and how flowR handles them
Readonlyenvironment: {Semantics regarding the handling of the environment
ReadonlyoverwriteBuiltIns: {Do you want to overwrite (parts) of the builtin definition?
Readonlydefinitions: BuiltInDefinition<The definitions to load
Optional ReadonlyloadDefaults?: booleanShould the default configuration still be loaded?
ReadonlysolverHow to resolve constants, constraints, cells, …
ReadonlyevalStrings: booleanShould we include eval(parse(text="...")) calls in the dataflow graph?
Readonlyinstrument: {These keys are only intended for use within code, allowing to instrument the dataflow analyzer!
OptionaldataflowExtractors?: (Modify the dataflow processors used during dataflow analysis. Make sure that all processors required for correct analysis are still present! This may have arbitrary consequences on the analysis precision and performance, consider focusing on decorating existing processors instead of replacing them.
ReadonlypointerTracking: boolean | { maxIndexCount: number }Whether to track pointers in the dataflow graph, if not, the graph will be over-approximated wrt. containers and accesses
Optional ReadonlyresolveSource?: FlowrLaxSourcingOptionsIf lax source calls are active, flowR searches for sourced files much more freely, based on the configurations you give it. This option is only in effect if ignoreSourceCalls is set to false.
Optionalslicer?: { threshold?: number }The configuration for flowR's slicer
Optional Readonlythreshold?: numberThe maximum number of iterations to perform on a single function call during slicing
Readonlyvariables: VariableResolveHow to resolve variables and their values
Configuration options for abstract interpretation