Executive summary
TouK/nussknacker is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has buttons or links with no name. It scores 37 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 27, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the password or key in the code, worth about 4 points. Structuring the pages would lift Accessibility itself, worth about 5 points. Raising Accessibility to 70 would lift the score to about 45.
104 known security holes in the packages the code depends on can be used by attackers. Sixty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and fifteen secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the three automatic dependency updates that take new releases at once, and passing outside input through environment variables would deal with the two pipeline steps that put outside input straight into a shell command. The 17 loops of files that import each other need breaking.
The product code is 182,261 lines, about €320,000 to rebuild.
If Accessibility rose from 27 to 70, the lowest score rated Strong, the score would rise from 37 to about 45.
New since the last survey: 81 findings
- Explicit Debt · TodoComment repeated across 14 files utils/flink-components-testkit/src/main/scala/pl/touk/nussknacker/engine/flink/util/test/TestResultSinkFactory.scala
- Secrets (history) · REDACTED
- Secrets (history) · REDACTED
- Secrets (history) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Knowledge Freshness · Orphaned knowledge scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Dependency Freshness · Dependency Freshness
- Web-Security Posture · Weak hash algorithm engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala
- Web-Security Posture · Weak hash algorithm engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/UberJarAssembler.scala
- Exception handling · Swallowed exception (empty catch) designer/client/src/windowManager/LoadingButton.tsx
- Exception handling · Swallowed exception (empty catch) designer/client/src/store/draftListener.ts
- Exception handling · Swallowed exception (empty catch) designer/client/src/store/draftListener.ts
- Exception handling · Swallowed exception (empty catch) designer/client/src/store/draftListener.ts
- Exception handling · Swallowed exception (empty catch) REDACTED
- Exception handling · Swallowed exception (caught, then discarded) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts
- Exception handling · Swallowed exception (caught, then discarded) designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts
- Exception handling · Swallowed exception (caught, then discarded) designer/client/src/components/modals/saveScenario/useSaveScenario.ts
- Exception handling · Swallowed exception (empty catch) designer/client/src/components/modals/TestingDataRecords/parseRecords.ts
- Exception handling · Swallowed exception (empty catch) designer/client/src/components/modals/TestingDataRecords/parseRecords.ts
- Exception handling · Swallowed exception (empty catch) designer/client/src/components/graph/SelectionContextProvider.tsx
- Exception handling · Swallowed exception (empty catch) designer/client/src/components/graph/SelectionContextProvider.tsx
- Exception handling · Swallowed exception (empty catch) designer/client/src/components/graph/node-modal/Variable.tsx
- Exception handling · Swallowed exception (empty catch) designer/client/src/components/graph/node-modal/io/RawDisplay.tsx
- Forms & labels · <TextField> field component without a label designer/client/src/components/dataMapper/FieldRow.tsx
Fixed since the last survey: 1524 findings
- Explicit Debt · TodoComment repeated across 14 files engine/flink/components-api/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinformation/SimpleTypeInformation.scala
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing REDACTED
- Code Duplication · Duplicated block (17 lines × 2 locations) designer/client/src/components/toolbars/activities/helpers/activityItemColors.ts
- Code Duplication · Duplicated block (17 lines × 3 locations) designer/client/src/components/toolbars/process/buttons/SaveButton.tsx
- Code Duplication · Duplicated block (17 lines × 2 locations) designer/client/src/components/toolbars/view/buttons/ZoomInButton.tsx
- Code Duplication · Duplicated block (16 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateEditor.tsx
- Code Duplication · Duplicated block (16 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx
- Code Duplication · Duplicated block (16 lines × 4 locations) designer/client/src/components/toolbars/process/buttons/SaveButton.tsx
- Code Duplication · Duplicated block (15 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts
- Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (15 lines × 2 locations) designer/client/src/components/graph/node-modal/SourceSinkCommon.tsx
- Code Duplication · Duplicated block (15 lines × 2 locations) designer/submodules/packages/components/src/scenarios/useScenariosQuery.tsx
- Code Duplication · Duplicated block (14 lines × 2 locations) designer/client/src/components/common/error-boundary/fallbackComponent/PlaceholderIconFallbackComponent.tsx
- Code Duplication · Duplicated block (14 lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionBuilderComponent.tsx
- Code Duplication · Duplicated block (14 lines × 2 locations) designer/submodules/packages/components/src/scenarios/filters/processingModeStack.tsx
- Code Duplication · Duplicated block (13 lines × 2 locations) designer/client/src/components/ComponentPreview.tsx
- Code Duplication · Duplicated block (13 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) designer/client/src/components/graph/node-modal/io/RawDisplay.tsx
- Code Duplication · Duplicated block (13 lines × 2 locations) designer/submodules/packages/components/src/components/usages/componentView.tsx
- Code Duplication · Duplicated block (12 lines × 2 locations) designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/InputDataRecords.tsx
- Code Duplication · Duplicated block (12 lines × 2 locations) designer/client/src/containers/settings/SearchField.tsx
- Code Duplication · Duplicated block (12 lines × 6 locations) designer/client/src/http/HttpService/HttpService.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) designer/submodules/packages/components/src/components/listWithFilters.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/actions/nk/selection.ts
- Code Duplication · Duplicated block (11 lines × 3 locations) designer/client/src/components/conditionBuilder/ConditionBuilderComponent.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/dataMapper/FieldRow.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/DataMapperComponent.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/customNode.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateEditor.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/Formatter.ts
- Code Duplication · Duplicated block (11 lines × 3 locations) designer/client/src/components/graph/node-modal/editors/expression/Formatter.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/Assertions.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts
- Code Duplication · Duplicated block (11 lines × 3 locations) designer/client/src/components/toolbars/scenarioActions/buttons/CancelDeployButton.tsx
- Code Duplication · Duplicated block (11 lines × 2 locations) designer/submodules/packages/components/src/components/usages/filtersPart.tsx
- Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx
- Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/modals/AddAttachmentDialog.tsx
- Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/modals/GenericConfirmDialog.tsx
- Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItemComment.tsx
- Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItemHeader.tsx
- Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/toolbars/process/buttons/SaveButton.tsx
- Code Duplication · Duplicated block (10 lines × 2 locations) designer/client/src/components/toolbars/search/utils.ts
Rebuild cost: about €320,000 · Estimate
| Cost to rebuild | €110,000 to €540,000, for 1,778 to 5,639 hours of work, about 2.2 person-years for 1 to 5 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 37. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Large: 182,261 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 designer.client.src.components.common.error-boundary.DefaultFullScreenMessage | 2 pl.touk.nussknacker.engine.api.typed.typing | 3 pl.touk.nussknacker.engine.graph.expression.Expression.Language | 4 pl.touk.nussknacker.engine.graph.expression.TabularTypedData | 5 pl.touk.nussknacker.engine.graph.expression | 6 pl.touk.nussknacker.engine.api.parameter | 7 pl.touk.nussknacker.engine.graph.node | 8 pl.touk.nussknacker.engine.graph.node.VariableOperation | 9 pl.touk.nussknacker.engine.api.process | 10 pl.touk.nussknacker.engine.api.context.ProcessCompilationError | 11 pl.touk.nussknacker.engine.api.context | 12 pl.touk.nussknacker.engine.api.context.transformation | 13 pl.touk.nussknacker.engine.api.definition | 14 pl.touk.nussknacker.engine.api.component | 15 pl.touk.nussknacker.engine.api | 16 pl.touk.nussknacker.engine.api.graph | 17 pl.touk.nussknacker.engine.expression.parse | 18 pl.touk.nussknacker.engine.flink.api.process | 19 pl.touk.nussknacker.engine.util | 20 pl.touk.nussknacker.ui.security.api | 21 pl.touk.nussknacker.engine.canonicalgraph | 22 pl.touk.nussknacker.engine.deployment | 23 pl.touk.nussknacker.engine.kafka | 24 pl.touk.nussknacker.engine.spel | 25 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos | 26 pl.touk.nussknacker.engine.compile | 27 pl.touk.nussknacker.ui.db.entity | 28 pl.touk.nussknacker.engine.compile.nodecompilation | 29 pl.touk.nussknacker.ui.process.repository | 30 pl.touk.nussknacker.engine.definition.component | 31 pl.touk.nussknacker.ui.process | 32 pl.touk.nussknacker.ui.process.deployment | 33 pl.touk.nussknacker.ui.api | 34 pl.touk.nussknacker.ui.config | 35 pl.touk.nussknacker.ui.process.processingtype | 36 pl.touk.nussknacker.engine.api.deployment | 37 pl.touk.nussknacker.engine | 38 pl.touk.nussknacker.ui.process.newdeployment | 39 pl.touk.nussknacker.ui.statistics | 40 pl.touk.nussknacker.ui.factory |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 designer.client.src.components.common.error-boundary.DefaultFullScreenMessage | ||||||||||||||||||||||||||||||||||||||||
| 2 pl.touk.nussknacker.engine.api.typed.typing | ||||||||||||||||||||||||||||||||||||||||
| 3 pl.touk.nussknacker.engine.graph.expression.Expression.Language | ||||||||||||||||||||||||||||||||||||||||
| 4 pl.touk.nussknacker.engine.graph.expression.TabularTypedData | ||||||||||||||||||||||||||||||||||||||||
| 5 pl.touk.nussknacker.engine.graph.expression | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 pl.touk.nussknacker.engine.api.parameter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 pl.touk.nussknacker.engine.graph.node | 6 | 1 | 37 | |||||||||||||||||||||||||||||||||||||
| 8 pl.touk.nussknacker.engine.graph.node.VariableOperation | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 pl.touk.nussknacker.engine.api.process | 3 | 1 | 3 | 4 | 1 | 4 | 10 | 2 | ||||||||||||||||||||||||||||||||
| 10 pl.touk.nussknacker.engine.api.context.ProcessCompilationError | 1 | 1 | 40 | 26 | 1 | 75 | 3 | 89 | ||||||||||||||||||||||||||||||||
| 11 pl.touk.nussknacker.engine.api.context | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 12 pl.touk.nussknacker.engine.api.context.transformation | 8 | 1 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 13 pl.touk.nussknacker.engine.api.definition | 4 | 2 | 12 | 26 | 12 | 13 | 4 | 23 | ||||||||||||||||||||||||||||||||
| 14 pl.touk.nussknacker.engine.api.component | 1 | 4 | 7 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 15 pl.touk.nussknacker.engine.api | 4 | 3 | 1 | 1 | 6 | 5 | ||||||||||||||||||||||||||||||||||
| 16 pl.touk.nussknacker.engine.api.graph | 2 | 2 | 5 | |||||||||||||||||||||||||||||||||||||
| 17 pl.touk.nussknacker.engine.expression.parse | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 pl.touk.nussknacker.engine.flink.api.process | 2 | 5 | 1 | 2 | 25 | |||||||||||||||||||||||||||||||||||
| 19 pl.touk.nussknacker.engine.util | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 20 pl.touk.nussknacker.ui.security.api | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 pl.touk.nussknacker.engine.canonicalgraph | 2 | 2 | 3 | 1 | 5 | 2 | ||||||||||||||||||||||||||||||||||
| 22 pl.touk.nussknacker.engine.deployment | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 pl.touk.nussknacker.engine.kafka | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 pl.touk.nussknacker.engine.spel | 10 | 4 | 4 | 1 | 3 | 3 | 1 | |||||||||||||||||||||||||||||||||
| 25 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos | 7 | 1 | 4 | 3 | 7 | 3 | 2 | 6 | 1 | |||||||||||||||||||||||||||||||
| 26 pl.touk.nussknacker.engine.compile | 1 | 2 | 9 | 2 | 4 | 1 | 10 | 3 | 2 | 13 | 2 | 6 | 6 | 9 | ||||||||||||||||||||||||||
| 27 pl.touk.nussknacker.ui.db.entity | 22 | 2 | 1 | 3 | 1 | 15 | ||||||||||||||||||||||||||||||||||
| 28 pl.touk.nussknacker.engine.compile.nodecompilation | 8 | 1 | 7 | 2 | 1 | 1 | 16 | 1 | 6 | 1 | 17 | 3 | 3 | 1 | 1 | |||||||||||||||||||||||||
| 29 pl.touk.nussknacker.ui.process.repository | 5 | 32 | 6 | 1 | 11 | 4 | 6 | 3 | 1 | 22 | ||||||||||||||||||||||||||||||
| 30 pl.touk.nussknacker.engine.definition.component | 3 | 1 | 1 | 1 | 3 | 24 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||
| 31 pl.touk.nussknacker.ui.process | 12 | 1 | 3 | 10 | 1 | 8 | 11 | |||||||||||||||||||||||||||||||||
| 32 pl.touk.nussknacker.ui.process.deployment | 2 | 1 | 5 | 2 | 6 | 4 | 1 | 7 | 5 | 6 | 3 | 10 | ||||||||||||||||||||||||||||
| 33 pl.touk.nussknacker.ui.api | 1 | 20 | 1 | 6 | 3 | 18 | 1 | 1 | 8 | 1 | 10 | 4 | 1 | |||||||||||||||||||||||||||
| 34 pl.touk.nussknacker.ui.config | 3 | 2 | 9 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 pl.touk.nussknacker.ui.process.processingtype | 1 | 1 | 7 | 2 | 4 | 1 | 1 | 2 | 2 | 11 | 4 | |||||||||||||||||||||||||||||
| 36 pl.touk.nussknacker.engine.api.deployment | 1 | 4 | 10 | 1 | 1 | 4 | 4 | 4 | 2 | |||||||||||||||||||||||||||||||
| 37 pl.touk.nussknacker.engine | 2 | 4 | 1 | 1 | 7 | 12 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||
| 38 pl.touk.nussknacker.ui.process.newdeployment | 1 | 2 | 8 | 2 | 3 | 6 | 1 | 1 | 1 | 6 | ||||||||||||||||||||||||||||||
| 39 pl.touk.nussknacker.ui.statistics | 2 | 2 | 1 | 2 | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 40 pl.touk.nussknacker.ui.factory | 1 | 5 | 1 | 2 | 2 | 1 | 2 | 1 | 1 |
5→4 pl.touk.nussknacker.engine.graph.expression uses pl.touk.nussknacker.engine.graph.expression.TabularTypedData✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.graph.expression uses a type in pl.touk.nussknacker.engine.graph.expression.TabularTypedData.
- The types involved
pl.touk.nussknacker.engine.graph.expression.TabularTypedData→pl.touk.nussknacker.engine.graph.expression.TabularTypedData.Columnpl.touk.nussknacker.engine.graph.expression.TabularTypedData→pl.touk.nussknacker.engine.graph.expression.TabularTypedData.Row
- Direction
- pl.touk.nussknacker.engine.graph.expression uses pl.touk.nussknacker.engine.graph.expression.TabularTypedData, so a change to pl.touk.nussknacker.engine.graph.expression.TabularTypedData can break pl.touk.nussknacker.engine.graph.expression, while a change to pl.touk.nussknacker.engine.graph.expression can't break pl.touk.nussknacker.engine.graph.expression.TabularTypedData.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.graph.expression uses a module listed above it, which is the healthy direction.
5→15 pl.touk.nussknacker.engine.graph.expression uses pl.touk.nussknacker.engine.api part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.graph.expression uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.graph.expression.NodeExpressionId→pl.touk.nussknacker.engine.api.NodeId
- Direction
- pl.touk.nussknacker.engine.graph.expression uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.graph.expression, while a change to pl.touk.nussknacker.engine.graph.expression can't break pl.touk.nussknacker.engine.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→5 pl.touk.nussknacker.engine.api.parameter uses pl.touk.nussknacker.engine.graph.expression✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.parameter uses a type in pl.touk.nussknacker.engine.graph.expression.
- The types involved
pl.touk.nussknacker.engine.api.parameter.ParameterValueCompileTimeValidation→pl.touk.nussknacker.engine.graph.expression.Expression
- Direction
- pl.touk.nussknacker.engine.api.parameter uses pl.touk.nussknacker.engine.graph.expression, so a change to pl.touk.nussknacker.engine.graph.expression can break pl.touk.nussknacker.engine.api.parameter, while a change to pl.touk.nussknacker.engine.api.parameter can't break pl.touk.nussknacker.engine.graph.expression.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.parameter uses a module listed above it, which is the healthy direction.
6→13 pl.touk.nussknacker.engine.api.parameter uses pl.touk.nussknacker.engine.api.definition part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.parameter uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.api.parameter.ValueInputWithFixedValuesProvided→pl.touk.nussknacker.engine.api.definition.FixedExpressionValue
- Direction
- pl.touk.nussknacker.engine.api.parameter uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.api.parameter, while a change to pl.touk.nussknacker.engine.api.parameter can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→5 pl.touk.nussknacker.engine.graph.node uses pl.touk.nussknacker.engine.graph.expression✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.engine.graph.node uses a type in pl.touk.nussknacker.engine.graph.expression.
- The types involved
pl.touk.nussknacker.engine.graph.node.Case→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.graph.node.Enricher→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.graph.node.Filter→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.graph.node.Sink→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.graph.node.Switch→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.graph.node.Variable→pl.touk.nussknacker.engine.graph.expression.Expression
- Direction
- pl.touk.nussknacker.engine.graph.node uses pl.touk.nussknacker.engine.graph.expression, so a change to pl.touk.nussknacker.engine.graph.expression can break pl.touk.nussknacker.engine.graph.node, while a change to pl.touk.nussknacker.engine.graph.node can't break pl.touk.nussknacker.engine.graph.expression.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.graph.node uses a module listed above it, which is the healthy direction.
7→9 pl.touk.nussknacker.engine.graph.node uses pl.touk.nussknacker.engine.api.process part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.graph.node uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.graph.node.NodeData→pl.touk.nussknacker.engine.api.process.Source
- Direction
- pl.touk.nussknacker.engine.graph.node uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.graph.node, while a change to pl.touk.nussknacker.engine.graph.node can't break pl.touk.nussknacker.engine.api.process.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→15 pl.touk.nussknacker.engine.graph.node uses pl.touk.nussknacker.engine.api part of a loop✕
- Connections
- 37 pairs of types, where a type in pl.touk.nussknacker.engine.graph.node uses a type in pl.touk.nussknacker.engine.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
pl.touk.nussknacker.engine.graph.node.BranchEndData→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.BranchEndData→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.BranchEndDefinition→pl.touk.nussknacker.engine.api.JoinReferencepl.touk.nussknacker.engine.graph.node.CustomNode→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.CustomNode→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.Enricher→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.Enricher→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.Filter→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.Filter→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.FragmentInput→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.FragmentInput→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.FragmentInputDefinition→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.FragmentInputDefinition→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.FragmentOutputDefinition→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.FragmentOutputDefinition→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.FragmentUsageOutput→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.FragmentUsageOutput→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.Join→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.Join→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.NodeData→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.NodeData→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.NodeWithData→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.Processor→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.graph.node.Processor→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.graph.node.Sink→pl.touk.nussknacker.engine.api.NodeId
- Direction
- pl.touk.nussknacker.engine.graph.node uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.graph.node, while a change to pl.touk.nussknacker.engine.graph.node can't break pl.touk.nussknacker.engine.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→7 pl.touk.nussknacker.engine.graph.node.VariableOperation uses pl.touk.nussknacker.engine.graph.node✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.graph.node.VariableOperation uses a type in pl.touk.nussknacker.engine.graph.node.
- The types involved
pl.touk.nussknacker.engine.graph.node.VariableOperation.Set→pl.touk.nussknacker.engine.graph.node.VariableOperationpl.touk.nussknacker.engine.graph.node.VariableOperation.Unset→pl.touk.nussknacker.engine.graph.node.VariableOperation
- Direction
- pl.touk.nussknacker.engine.graph.node.VariableOperation uses pl.touk.nussknacker.engine.graph.node, so a change to pl.touk.nussknacker.engine.graph.node can break pl.touk.nussknacker.engine.graph.node.VariableOperation, while a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can't break pl.touk.nussknacker.engine.graph.node.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.graph.node.VariableOperation uses a module listed above it, which is the healthy direction.
9→2 pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.api.process uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.api.process.BasicContextInitializer→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.process.TypingFunctionForClassMember→pl.touk.nussknacker.engine.api.typed.typing.SingleTypingResultpl.touk.nussknacker.engine.api.process.TypingFunctionForClassMember→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.api.process, while a change to pl.touk.nussknacker.engine.api.process can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.process uses a module listed above it, which is the healthy direction.
9→6 pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.process uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.engine.api.process.TestWithParametersSupport→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.api.process, while a change to pl.touk.nussknacker.engine.api.process can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.process uses a module listed above it, which is the healthy direction.
9→8 pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.api.process uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation.
- The types involved
pl.touk.nussknacker.engine.api.process.AllMembersPredicate→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.process.ClassNamePredicate→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.process.MemberNamePredicate→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.engine.api.process, while a change to pl.touk.nussknacker.engine.api.process can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.process uses a module listed above it, which is the healthy direction.
9→11 pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.context part of a loop✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api.process uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.engine.api.process.BasicContextInitializer→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.process.BasicContextInitializer→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.api.process.ContextInitializer→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.process.ContextInitializer→pl.touk.nussknacker.engine.api.context.ValidationContext
- Direction
- pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine.api.process, while a change to pl.touk.nussknacker.engine.api.process can't break pl.touk.nussknacker.engine.api.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→13 pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.definition part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.process uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.api.process.TestWithParametersSupport→pl.touk.nussknacker.engine.api.definition.Parameter
- Direction
- pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.api.process, while a change to pl.touk.nussknacker.engine.api.process can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→14 pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.component part of a loop✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api.process uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.api.process.SinkFactory→pl.touk.nussknacker.engine.api.component.AllProcessingModesComponentpl.touk.nussknacker.engine.api.process.SinkFactory→pl.touk.nussknacker.engine.api.component.Componentpl.touk.nussknacker.engine.api.process.SourceFactory→pl.touk.nussknacker.engine.api.component.Componentpl.touk.nussknacker.engine.api.process.WithCategories→pl.touk.nussknacker.engine.api.component.ComponentConfig
- Direction
- pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.api.process, while a change to pl.touk.nussknacker.engine.api.process can't break pl.touk.nussknacker.engine.api.component.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→15 pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api part of a loop✕
- Connections
- 10 pairs of types, where a type in pl.touk.nussknacker.engine.api.process uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.api.process.BasicContextInitializer→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.process.ContextInitializer→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.process.EmptyProcessConfigCreator→pl.touk.nussknacker.engine.api.CustomStreamTransformerpl.touk.nussknacker.engine.api.process.EmptyProcessConfigCreator→pl.touk.nussknacker.engine.api.ProcessListenerpl.touk.nussknacker.engine.api.process.EmptyProcessConfigCreator→pl.touk.nussknacker.engine.api.Servicepl.touk.nussknacker.engine.api.process.ExpressionConfig→pl.touk.nussknacker.engine.api.ConversionsProviderpl.touk.nussknacker.engine.api.process.ExpressionConfig→pl.touk.nussknacker.engine.api.SpelExpressionExcludeListpl.touk.nussknacker.engine.api.process.ProcessConfigCreator→pl.touk.nussknacker.engine.api.CustomStreamTransformerpl.touk.nussknacker.engine.api.process.ProcessConfigCreator→pl.touk.nussknacker.engine.api.ProcessListenerpl.touk.nussknacker.engine.api.process.ProcessConfigCreator→pl.touk.nussknacker.engine.api.Service
- Direction
- pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.api.process, while a change to pl.touk.nussknacker.engine.api.process can't break pl.touk.nussknacker.engine.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→37 pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine part of a loop✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.api.process uses a type in pl.touk.nussknacker.engine.
- The types involved
pl.touk.nussknacker.engine.api.process.EmptyProcessConfigCreator→pl.touk.nussknacker.engine.ModelConfigpl.touk.nussknacker.engine.api.process.ProcessConfigCreator→pl.touk.nussknacker.engine.ModelConfig
- Direction
- pl.touk.nussknacker.engine.api.process uses pl.touk.nussknacker.engine, so a change to pl.touk.nussknacker.engine can break pl.touk.nussknacker.engine.api.process, while a change to pl.touk.nussknacker.engine.api.process can't break pl.touk.nussknacker.engine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictIsOfInvalidType→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.api.context.ProcessCompilationError, while a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a module listed above it, which is the healthy direction.
10→3 pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.graph.expression.Expression.Language✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a type in pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError.MultiSelectUnallowedValue→pl.touk.nussknacker.engine.graph.expression.Expression.Language.Json
- Direction
- pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.graph.expression.Expression.Language, so a change to pl.touk.nussknacker.engine.graph.expression.Expression.Language can break pl.touk.nussknacker.engine.api.context.ProcessCompilationError, while a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can't break pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a module listed above it, which is the healthy direction.
10→6 pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 40 pairs of types, where a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a type in pl.touk.nussknacker.engine.api.parameter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError.BlankParameter→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.CompileTimeEvaluableParameterNotEvaluated→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.CustomNodeError→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.CustomParameterValidationError→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictEntryWithKeyNotExists→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictEntryWithLabelNotExists→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictIsOfInvalidType→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictLabelByKeyResolutionFailed→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictNotDeclared→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateFragmentInputParameter→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedParameters→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.EagerExpressionEvaluationError→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyFixedListForRequiredField→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyMandatoryField→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyMandatoryParameter→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.ExpressionParserCompilationError→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.ExpressionParserCompilationErrorInFragmentDefinition→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.FragmentParamClassLoadError→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.GreaterThanRequiredParameter→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.IncompatibleParameterDefinitionModification→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.InitialValueNotPresentInPossibleValues→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidDurationParameter→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidIntegerLiteralParameter→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidPropertyFixedValue→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidValidationExpression→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.api.context.ProcessCompilationError, while a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a module listed above it, which is the healthy direction.
10→8 pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 26 pairs of types, where a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError.DisablingManyOutputsFragment→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DisablingNoOutputsFragment→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateCustomNodeOutputNames→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateFragmentOutputNamesInFragment→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedNodeIds→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedNodeNames→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedParameters→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyFixedListForRequiredField→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyProcess→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.FatalUnknownError→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.FragmentOutputNotDefined→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.InASingleNode→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.InitialValueNotPresentInPossibleValues→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidRootNode→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidTailOfBranch→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.LooseNode→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.MissingCustomNodeOutputName→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.MissingParameters→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.MultipleOutputsToSameJoin→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.ScenarioPropertiesError→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.UnknownCustomNodeOutput→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.UnknownFragmentOutput→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.UnsupportedDictParameterEditorType→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.UnsupportedEdgeNextToCustomNodeOutputs→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.context.ProcessCompilationError.UnsupportedFixedValuesType→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.engine.api.context.ProcessCompilationError, while a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a module listed above it, which is the healthy direction.
10→9 pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError.ScenarioNameError→pl.touk.nussknacker.engine.api.process.ProcessName
- Direction
- pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.api.context.ProcessCompilationError, while a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a module listed above it, which is the healthy direction.
10→11 pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.context part of a loop✕
- Connections
- 75 pairs of types, where a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a type in pl.touk.nussknacker.engine.api.context. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError.BlankParameter→pl.touk.nussknacker.engine.api.context.ParameterValidationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.CannotCreateObjectError→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.CompileTimeEvaluableParameterNotEvaluated→pl.touk.nussknacker.engine.api.context.ParameterValidationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.CustomNodeError→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.CustomParameterValidationError→pl.touk.nussknacker.engine.api.context.ParameterValidationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictEntryWithKeyNotExists→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictEntryWithLabelNotExists→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictIsOfInvalidType→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictLabelByKeyResolutionFailed→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictNotDeclared→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DisabledNode→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DisablingManyOutputsFragment→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DisablingNoOutputsFragment→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateCustomNodeOutputNames→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateFragmentInputParameter→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateFragmentOutputNames→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedNodeIds→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedNodeNames→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedParameters→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.EagerExpressionEvaluationError→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyFixedListForRequiredField→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyMandatoryField→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyMandatoryParameter→pl.touk.nussknacker.engine.api.context.ParameterValidationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyProcess→pl.touk.nussknacker.engine.api.context.ProcessUncanonizationErrorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.ExpressionParserCompilationError→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationError
- Direction
- pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine.api.context.ProcessCompilationError, while a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can't break pl.touk.nussknacker.engine.api.context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→13 pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.definition part of a loop✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError.IncompatibleParameterDefinitionModification→pl.touk.nussknacker.engine.api.definition.ParameterEditorpl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidPropertyFixedValue→pl.touk.nussknacker.engine.api.definition.FixedExpressionValuepl.touk.nussknacker.engine.api.context.ProcessCompilationError.MultiSelectUnallowedValue→pl.touk.nussknacker.engine.api.definition.MultiSelectFixedValue
- Direction
- pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.api.context.ProcessCompilationError, while a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→15 pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api part of a loop✕
- Connections
- 89 pairs of types, where a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses a type in pl.touk.nussknacker.engine.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError.BlankParameter→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.CannotCreateObjectError→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.CannotCreateObjectError→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.CompileTimeEvaluableParameterNotEvaluated→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.CustomNodeError→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.CustomParameterValidationError→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictEntryWithKeyNotExists→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictEntryWithLabelNotExists→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictIsOfInvalidType→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictLabelByKeyResolutionFailed→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DictNotDeclared→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DisabledNode→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DisabledNode→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DisablingManyOutputsFragment→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DisablingNoOutputsFragment→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateCustomNodeOutputNames→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateFragmentInputParameter→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateFragmentOutputNamesInFragment→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicateFragmentOutputNamesInScenario→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedNodeIds→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedNodeIds→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedNodeNames→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedNodeNames→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.api.context.ProcessCompilationError.DuplicatedParameters→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.ProcessCompilationError.EagerExpressionEvaluationError→pl.touk.nussknacker.engine.api.NodeId
- Direction
- pl.touk.nussknacker.engine.api.context.ProcessCompilationError uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.api.context.ProcessCompilationError, while a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can't break pl.touk.nussknacker.engine.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→6 pl.touk.nussknacker.engine.api.context uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.context uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.engine.api.context.ParameterValidationError→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.engine.api.context uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.api.context, while a change to pl.touk.nussknacker.engine.api.context can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context uses a module listed above it, which is the healthy direction.
11→8 pl.touk.nussknacker.engine.api.context uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.context uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.engine.api.context uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.engine.api.context, while a change to pl.touk.nussknacker.engine.api.context can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context uses a module listed above it, which is the healthy direction.
11→10 pl.touk.nussknacker.engine.api.context uses pl.touk.nussknacker.engine.api.context.ProcessCompilationError✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.context uses a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError.
- The types involved
pl.touk.nussknacker.engine.api.context.ParameterValidationError→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.InASingleNode
- Direction
- pl.touk.nussknacker.engine.api.context uses pl.touk.nussknacker.engine.api.context.ProcessCompilationError, so a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can break pl.touk.nussknacker.engine.api.context, while a change to pl.touk.nussknacker.engine.api.context can't break pl.touk.nussknacker.engine.api.context.ProcessCompilationError.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context uses a module listed above it, which is the healthy direction.
11→15 pl.touk.nussknacker.engine.api.context uses pl.touk.nussknacker.engine.api part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.context uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.api.context.ProcessCompilationError→pl.touk.nussknacker.engine.api.NodeId
- Direction
- pl.touk.nussknacker.engine.api.context uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.api.context, while a change to pl.touk.nussknacker.engine.api.context can't break pl.touk.nussknacker.engine.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→2 pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 8 pairs of types, where a type in pl.touk.nussknacker.engine.api.context.transformation uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.api.context.transformation.BaseDefinedParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.context.transformation.DefinedBranchParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.context.transformation.DefinedEagerBranchParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.context.transformation.DefinedEagerParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.context.transformation.DefinedLazyBranchParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.context.transformation.DefinedLazyParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.context.transformation.FailedToDefineParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.context.transformation.ValidDefinedSingleParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.api.context.transformation, while a change to pl.touk.nussknacker.engine.api.context.transformation can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context.transformation uses a module listed above it, which is the healthy direction.
12→11 pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.context.transformation uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.engine.api.context.transformation.FailedToDefineParameter→pl.touk.nussknacker.engine.api.context.ProcessCompilationError
- Direction
- pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine.api.context.transformation, while a change to pl.touk.nussknacker.engine.api.context.transformation can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.context.transformation uses a module listed above it, which is the healthy direction.
12→13 pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api.definition part of a loop✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.api.context.transformation uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.api.context.transformation.DynamicComponent→pl.touk.nussknacker.engine.api.definition.NodeDependencypl.touk.nussknacker.engine.api.context.transformation.WithStaticParameters→pl.touk.nussknacker.engine.api.definition.Parameter
- Direction
- pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.api.context.transformation, while a change to pl.touk.nussknacker.engine.api.context.transformation can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→14 pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api.component part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.context.transformation uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.api.context.transformation.DynamicComponent→pl.touk.nussknacker.engine.api.component.Component
- Direction
- pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.api.context.transformation, while a change to pl.touk.nussknacker.engine.api.context.transformation can't break pl.touk.nussknacker.engine.api.component.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→15 pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api part of a loop✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.api.context.transformation uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.api.context.transformation.DynamicComponent→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.context.transformation.DynamicComponent→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.api.context.transformation.DynamicComponent→pl.touk.nussknacker.engine.api.Params
- Direction
- pl.touk.nussknacker.engine.api.context.transformation uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.api.context.transformation, while a change to pl.touk.nussknacker.engine.api.context.transformation can't break pl.touk.nussknacker.engine.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→2 pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api.definition uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.api.definition.AdditionalVariable→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.definition.NotBlankParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.definition.Parameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.definition.WithExplicitTypesToExtract→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.api.definition, while a change to pl.touk.nussknacker.engine.api.definition can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.definition uses a module listed above it, which is the healthy direction.
13→3 pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.graph.expression.Expression.Language✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.api.definition uses a type in pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- The types involved
pl.touk.nussknacker.engine.api.definition.MultiSelectFixedValue→pl.touk.nussknacker.engine.graph.expression.Expression.Language.Jsonpl.touk.nussknacker.engine.api.definition.MultiSelectFixedValuesExpressionValidator→pl.touk.nussknacker.engine.graph.expression.Expression.Language.Json
- Direction
- pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.graph.expression.Expression.Language, so a change to pl.touk.nussknacker.engine.graph.expression.Expression.Language can break pl.touk.nussknacker.engine.api.definition, while a change to pl.touk.nussknacker.engine.api.definition can't break pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.definition uses a module listed above it, which is the healthy direction.
13→5 pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.graph.expression✕
- Connections
- 12 pairs of types, where a type in pl.touk.nussknacker.engine.api.definition uses a type in pl.touk.nussknacker.engine.graph.expression.
- The types involved
pl.touk.nussknacker.engine.api.definition.CompileTimeAndRuntimeValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.CompileTimeEvaluableValueValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.CompileTimeNonNegativeDurationValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.CompileTimePositiveDurationValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.CompileTimeValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.FixedValuesExpressionValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.JsonExpressionValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.LiteralIntegerExpressionValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.MandatoryExpressionValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.MultiSelectFixedValuesExpressionValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.RuntimeValidator→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.api.definition.ValidationExpressionParameterValidatorToCompile→pl.touk.nussknacker.engine.graph.expression.Expression
- Direction
- pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.graph.expression, so a change to pl.touk.nussknacker.engine.graph.expression can break pl.touk.nussknacker.engine.api.definition, while a change to pl.touk.nussknacker.engine.api.definition can't break pl.touk.nussknacker.engine.graph.expression.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.definition uses a module listed above it, which is the healthy direction.
13→6 pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 26 pairs of types, where a type in pl.touk.nussknacker.engine.api.definition uses a type in pl.touk.nussknacker.engine.api.parameter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
pl.touk.nussknacker.engine.api.definition.CompileTimeAndRuntimeValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.CompileTimeEvaluableValueValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.CompileTimeNonNegativeDurationValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.CompileTimePositiveDurationValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.CompileTimeValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.FixedValuesExpressionValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.JsonExpressionValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.LiteralIntegerExpressionValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.MandatoryExpressionValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.MaximalNumberValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.MinimalNumberValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.MultiSelectFixedValuesExpressionValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.NonNegativeDurationValidation→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.NonNegativeDurationValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.NotBlankParameter→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.NotBlankValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.NotEmptyCollectionValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.NotNullValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.Parameter→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.ParameterDeclaration→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.ParameterExtractor→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.PositiveDurationValidation→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.PositiveDurationValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.RegExpValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.definition.RuntimeValidator→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.api.definition, while a change to pl.touk.nussknacker.engine.api.definition can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.definition uses a module listed above it, which is the healthy direction.
13→10 pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.context.ProcessCompilationError✕
- Connections
- 12 pairs of types, where a type in pl.touk.nussknacker.engine.api.definition uses a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError.
- The types involved
pl.touk.nussknacker.engine.api.definition.CompileTimeEvaluableValueValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.CompileTimeEvaluableParameterNotEvaluatedpl.touk.nussknacker.engine.api.definition.JsonExpressionValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.JsonRequiredParameterpl.touk.nussknacker.engine.api.definition.LiteralIntegerExpressionValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidIntegerLiteralParameterpl.touk.nussknacker.engine.api.definition.MandatoryExpressionValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyMandatoryParameterpl.touk.nussknacker.engine.api.definition.MaximalNumberValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.GreaterThanRequiredParameterpl.touk.nussknacker.engine.api.definition.MinimalNumberValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.LowerThanRequiredParameterpl.touk.nussknacker.engine.api.definition.NonNegativeDurationValidation→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidDurationParameterpl.touk.nussknacker.engine.api.definition.NotBlankValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.BlankParameterpl.touk.nussknacker.engine.api.definition.NotEmptyCollectionValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyMandatoryParameterpl.touk.nussknacker.engine.api.definition.NotNullValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.EmptyMandatoryParameterpl.touk.nussknacker.engine.api.definition.PositiveDurationValidation→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.InvalidDurationParameterpl.touk.nussknacker.engine.api.definition.RegExpValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.MismatchParameter
- Direction
- pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.context.ProcessCompilationError, so a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can break pl.touk.nussknacker.engine.api.definition, while a change to pl.touk.nussknacker.engine.api.definition can't break pl.touk.nussknacker.engine.api.context.ProcessCompilationError.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.definition uses a module listed above it, which is the healthy direction.
13→11 pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 13 pairs of types, where a type in pl.touk.nussknacker.engine.api.definition uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.engine.api.definition.CompileTimeAndRuntimeValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.CompileTimeEvaluableValueValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.CompileTimeNonNegativeDurationValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.CompileTimePositiveDurationValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.CompileTimeValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.FixedValuesExpressionValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.JsonExpressionValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.LiteralIntegerExpressionValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.MandatoryExpressionValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.MultiSelectFixedValuesExpressionValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.NonNegativeDurationValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.PositiveDurationValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.api.definition.ValidationExpressionParameterValidatorToCompile→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationError
- Direction
- pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine.api.definition, while a change to pl.touk.nussknacker.engine.api.definition can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.definition uses a module listed above it, which is the healthy direction.
13→12 pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.context.transformation✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api.definition uses a type in pl.touk.nussknacker.engine.api.context.transformation.
- The types involved
pl.touk.nussknacker.engine.api.definition.EngineScenarioCompilationDependencies→pl.touk.nussknacker.engine.api.context.transformation.TypedNodeDependencyValuepl.touk.nussknacker.engine.api.definition.OutputVariableNameDependency→pl.touk.nussknacker.engine.api.context.transformation.NodeDependencyValuepl.touk.nussknacker.engine.api.definition.TypedNodeDependency→pl.touk.nussknacker.engine.api.context.transformation.NodeDependencyValuepl.touk.nussknacker.engine.api.definition.ValueExtractor→pl.touk.nussknacker.engine.api.context.transformation.NodeDependencyValue
- Direction
- pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api.context.transformation, so a change to pl.touk.nussknacker.engine.api.context.transformation can break pl.touk.nussknacker.engine.api.definition, while a change to pl.touk.nussknacker.engine.api.definition can't break pl.touk.nussknacker.engine.api.context.transformation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.definition uses a module listed above it, which is the healthy direction.
13→15 pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api part of a loop✕
- Connections
- 23 pairs of types, where a type in pl.touk.nussknacker.engine.api.definition uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.api.definition.CompileTimeAndRuntimeValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.CompileTimeEvaluableValueValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.CompileTimeNonNegativeDurationValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.CompileTimePositiveDurationValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.CompileTimeValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.FixedValuesExpressionValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.JsonExpressionValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.LiteralIntegerExpressionValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.MandatoryExpressionValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.MaximalNumberValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.MinimalNumberValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.MultiSelectFixedValuesExpressionValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.NonNegativeDurationValidation→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.NonNegativeDurationValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.NotBlankValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.NotEmptyCollectionValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.NotNullValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.ParameterExtractor→pl.touk.nussknacker.engine.api.Paramspl.touk.nussknacker.engine.api.definition.PositiveDurationValidation→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.PositiveDurationValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.RegExpValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.RuntimeValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.definition.ValidationExpressionParameterValidatorToCompile→pl.touk.nussknacker.engine.api.NodeId
- Direction
- pl.touk.nussknacker.engine.api.definition uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.api.definition, while a change to pl.touk.nussknacker.engine.api.definition can't break pl.touk.nussknacker.engine.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→5 pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine.graph.expression✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.component uses a type in pl.touk.nussknacker.engine.graph.expression.
- The types involved
pl.touk.nussknacker.engine.api.component.ParameterConfig→pl.touk.nussknacker.engine.graph.expression.Expression
- Direction
- pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine.graph.expression, so a change to pl.touk.nussknacker.engine.graph.expression can break pl.touk.nussknacker.engine.api.component, while a change to pl.touk.nussknacker.engine.api.component can't break pl.touk.nussknacker.engine.graph.expression.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.component uses a module listed above it, which is the healthy direction.
14→6 pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api.component uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.engine.api.component.ComponentAdditionalConfig→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.component.ComponentConfig→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.api.component.ParameterAdditionalUIConfig→pl.touk.nussknacker.engine.api.parameter.ParameterValueCompileTimeValidationpl.touk.nussknacker.engine.api.component.ParameterAdditionalUIConfig→pl.touk.nussknacker.engine.api.parameter.ParameterValueInput
- Direction
- pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.api.component, while a change to pl.touk.nussknacker.engine.api.component can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.component uses a module listed above it, which is the healthy direction.
14→13 pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine.api.definition✕
- Connections
- 7 pairs of types, where a type in pl.touk.nussknacker.engine.api.component uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.api.component.ParameterConfig→pl.touk.nussknacker.engine.api.definition.ParameterCategorypl.touk.nussknacker.engine.api.component.ParameterConfig→pl.touk.nussknacker.engine.api.definition.ParameterEditorpl.touk.nussknacker.engine.api.component.ParameterConfig→pl.touk.nussknacker.engine.api.definition.ParameterValidatorpl.touk.nussknacker.engine.api.component.ScenarioPropertyConfig→pl.touk.nussknacker.engine.api.definition.ParameterValidatorpl.touk.nussknacker.engine.api.component.ScenarioPropertyConfig→pl.touk.nussknacker.engine.api.definition.StaticParameterEditorpl.touk.nussknacker.engine.api.component.StaticParameterConfig→pl.touk.nussknacker.engine.api.definition.ParameterValidatorpl.touk.nussknacker.engine.api.component.StaticParameterConfig→pl.touk.nussknacker.engine.api.definition.StaticParameterEditor
- Direction
- pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.api.component, while a change to pl.touk.nussknacker.engine.api.component can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.component uses a module listed above it, which is the healthy direction.
14→15 pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine.api part of a loop✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.api.component uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.api.component.NodeComponentInfo→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.component.NodeComponentInfo→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.api.component.NodesDeploymentData→pl.touk.nussknacker.engine.api.NodeId
- Direction
- pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.api.component, while a change to pl.touk.nussknacker.engine.api.component can't break pl.touk.nussknacker.engine.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→37 pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.component uses a type in pl.touk.nussknacker.engine.
- The types involved
pl.touk.nussknacker.engine.api.component.ComponentDependencies→pl.touk.nussknacker.engine.ModelConfig
- Direction
- pl.touk.nussknacker.engine.api.component uses pl.touk.nussknacker.engine, so a change to pl.touk.nussknacker.engine can break pl.touk.nussknacker.engine.api.component, while a change to pl.touk.nussknacker.engine.api.component can't break pl.touk.nussknacker.engine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→2 pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.api.BranchEagerParameterEvaluationResult→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.LazyParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.SingleEagerParameterEvaluationResult→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.api.SingleLazyParameterEvaluationResult→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.api, while a change to pl.touk.nussknacker.engine.api can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api uses a module listed above it, which is the healthy direction.
15→3 pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.graph.expression.Expression.Language✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.api uses a type in pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- The types involved
pl.touk.nussknacker.engine.api.CirceUtil→pl.touk.nussknacker.engine.graph.expression.Expression.Language.Jsonpl.touk.nussknacker.engine.api.DisplayJson→pl.touk.nussknacker.engine.graph.expression.Expression.Language.Jsonpl.touk.nussknacker.engine.api.DisplayJsonWithEncoder→pl.touk.nussknacker.engine.graph.expression.Expression.Language.Json
- Direction
- pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.graph.expression.Expression.Language, so a change to pl.touk.nussknacker.engine.graph.expression.Expression.Language can break pl.touk.nussknacker.engine.api, while a change to pl.touk.nussknacker.engine.api can't break pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api uses a module listed above it, which is the healthy direction.
15→4 pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.graph.expression.TabularTypedData✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api uses a type in pl.touk.nussknacker.engine.graph.expression.TabularTypedData.
- The types involved
pl.touk.nussknacker.engine.api.CirceUtil→pl.touk.nussknacker.engine.graph.expression.TabularTypedData.Error
- Direction
- pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.graph.expression.TabularTypedData, so a change to pl.touk.nussknacker.engine.graph.expression.TabularTypedData can break pl.touk.nussknacker.engine.api, while a change to pl.touk.nussknacker.engine.api can't break pl.touk.nussknacker.engine.graph.expression.TabularTypedData.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api uses a module listed above it, which is the healthy direction.
15→6 pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.engine.api.Params→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.api, while a change to pl.touk.nussknacker.engine.api can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api uses a module listed above it, which is the healthy direction.
15→9 pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.engine.api uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.api.ContextId→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.MetaData→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.ProcessVersion→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.engine.api.ProcessVersion→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.ProcessVersion→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.engine.api.ServiceInvoker→pl.touk.nussknacker.engine.api.process.ComponentUseContext
- Direction
- pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.api, while a change to pl.touk.nussknacker.engine.api can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api uses a module listed above it, which is the healthy direction.
15→14 pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.engine.api uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.api.CustomStreamTransformer→pl.touk.nussknacker.engine.api.component.AllProcessingModesComponentpl.touk.nussknacker.engine.api.CustomStreamTransformer→pl.touk.nussknacker.engine.api.component.Componentpl.touk.nussknacker.engine.api.CustomStreamTransformer→pl.touk.nussknacker.engine.api.component.ComponentOutputpl.touk.nussknacker.engine.api.Service→pl.touk.nussknacker.engine.api.component.AllProcessingModesComponentpl.touk.nussknacker.engine.api.Service→pl.touk.nussknacker.engine.api.component.Component
- Direction
- pl.touk.nussknacker.engine.api uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.api, while a change to pl.touk.nussknacker.engine.api can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api uses a module listed above it, which is the healthy direction.
16→7 pl.touk.nussknacker.engine.api.graph uses pl.touk.nussknacker.engine.graph.node✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.api.graph uses a type in pl.touk.nussknacker.engine.graph.node.
- The types involved
pl.touk.nussknacker.engine.api.graph.ScenarioGraph→pl.touk.nussknacker.engine.graph.node.NodeDatapl.touk.nussknacker.engine.api.graph.ScenarioGraph→pl.touk.nussknacker.engine.graph.node.StickyNote
- Direction
- pl.touk.nussknacker.engine.api.graph uses pl.touk.nussknacker.engine.graph.node, so a change to pl.touk.nussknacker.engine.graph.node can break pl.touk.nussknacker.engine.api.graph, while a change to pl.touk.nussknacker.engine.api.graph can't break pl.touk.nussknacker.engine.graph.node.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.graph uses a module listed above it, which is the healthy direction.
16→9 pl.touk.nussknacker.engine.api.graph uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.api.graph uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.api.graph.ProcessProperties→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.graph.ScenarioGraph→pl.touk.nussknacker.engine.api.process.ProcessName
- Direction
- pl.touk.nussknacker.engine.api.graph uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.api.graph, while a change to pl.touk.nussknacker.engine.api.graph can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.graph uses a module listed above it, which is the healthy direction.
16→15 pl.touk.nussknacker.engine.api.graph uses pl.touk.nussknacker.engine.api✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.engine.api.graph uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.api.graph.Edge→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.api.graph.ProcessProperties→pl.touk.nussknacker.engine.api.MetaDatapl.touk.nussknacker.engine.api.graph.ProcessProperties→pl.touk.nussknacker.engine.api.ProcessAdditionalFieldspl.touk.nussknacker.engine.api.graph.ProcessProperties→pl.touk.nussknacker.engine.api.TypeSpecificDatapl.touk.nussknacker.engine.api.graph.ScenarioGraph→pl.touk.nussknacker.engine.api.MetaData
- Direction
- pl.touk.nussknacker.engine.api.graph uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.api.graph, while a change to pl.touk.nussknacker.engine.api.graph can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.graph uses a module listed above it, which is the healthy direction.
17→2 pl.touk.nussknacker.engine.expression.parse uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.expression.parse uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.expression.parse.ExpressionParser→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.expression.parse.TypedExpression→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.expression.parse uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.expression.parse, while a change to pl.touk.nussknacker.engine.expression.parse can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.expression.parse uses a module listed above it, which is the healthy direction.
17→5 pl.touk.nussknacker.engine.expression.parse uses pl.touk.nussknacker.engine.graph.expression✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.expression.parse uses a type in pl.touk.nussknacker.engine.graph.expression.
- The types involved
pl.touk.nussknacker.engine.expression.parse.CompiledExpression→pl.touk.nussknacker.engine.graph.expression.Expression
- Direction
- pl.touk.nussknacker.engine.expression.parse uses pl.touk.nussknacker.engine.graph.expression, so a change to pl.touk.nussknacker.engine.graph.expression can break pl.touk.nussknacker.engine.expression.parse, while a change to pl.touk.nussknacker.engine.expression.parse can't break pl.touk.nussknacker.engine.graph.expression.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.expression.parse uses a module listed above it, which is the healthy direction.
17→11 pl.touk.nussknacker.engine.expression.parse uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.expression.parse uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.engine.expression.parse.ExpressionParser→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.expression.parse.SingleBranchTypedValue→pl.touk.nussknacker.engine.api.context.ValidationContext
- Direction
- pl.touk.nussknacker.engine.expression.parse uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine.expression.parse, while a change to pl.touk.nussknacker.engine.expression.parse can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.expression.parse uses a module listed above it, which is the healthy direction.
17→15 pl.touk.nussknacker.engine.expression.parse uses pl.touk.nussknacker.engine.api✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.expression.parse uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.expression.parse.CompiledExpression→pl.touk.nussknacker.engine.api.Context
- Direction
- pl.touk.nussknacker.engine.expression.parse uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.expression.parse, while a change to pl.touk.nussknacker.engine.expression.parse can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.expression.parse uses a module listed above it, which is the healthy direction.
18→2 pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.flink.api.process uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.flink.api.process.BasicFlinkSink→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.flink.api.process.FlinkCustomStreamTransformation→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.flink.api.process, while a change to pl.touk.nussknacker.engine.flink.api.process can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.flink.api.process uses a module listed above it, which is the healthy direction.
18→9 pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.engine.flink.api.process uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.flink.api.process.CustomizableContextInitializerSource→pl.touk.nussknacker.engine.api.process.ContextInitializerpl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext→pl.touk.nussknacker.engine.api.process.ComponentUseContextpl.touk.nussknacker.engine.flink.api.process.FlinkSink→pl.touk.nussknacker.engine.api.process.Sinkpl.touk.nussknacker.engine.flink.api.process.FlinkSource→pl.touk.nussknacker.engine.api.process.Sourcepl.touk.nussknacker.engine.flink.api.process.FlinkSourceTestSupport→pl.touk.nussknacker.engine.api.process.SourceTestSupport
- Direction
- pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.flink.api.process, while a change to pl.touk.nussknacker.engine.flink.api.process can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.flink.api.process uses a module listed above it, which is the healthy direction.
18→11 pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.flink.api.process uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext→pl.touk.nussknacker.engine.api.context.ValidationContext
- Direction
- pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine.flink.api.process, while a change to pl.touk.nussknacker.engine.flink.api.process can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.flink.api.process uses a module listed above it, which is the healthy direction.
18→14 pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.flink.api.process uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext→pl.touk.nussknacker.engine.api.component.ComponentOutputpl.touk.nussknacker.engine.flink.api.process.FlinkLazyParameterFunctionHelper→pl.touk.nussknacker.engine.api.component.NodeComponentInfo
- Direction
- pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.flink.api.process, while a change to pl.touk.nussknacker.engine.flink.api.process can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.flink.api.process uses a module listed above it, which is the healthy direction.
18→15 pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api✕
- Connections
- 25 pairs of types, where a type in pl.touk.nussknacker.engine.flink.api.process uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.flink.api.process.AbstractOneParamLazyParameterFunction→pl.touk.nussknacker.engine.api.LazyParameterpl.touk.nussknacker.engine.flink.api.process.BasicFlinkSink→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.BasicFlinkSink→pl.touk.nussknacker.engine.api.ValueWithContextpl.touk.nussknacker.engine.flink.api.process.FlinkContextInitializingFunction→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.FlinkCustomJoinTransformation→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.FlinkCustomJoinTransformation→pl.touk.nussknacker.engine.api.ValueWithContextpl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext→pl.touk.nussknacker.engine.api.MetaDatapl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext→pl.touk.nussknacker.engine.api.ValueWithContextpl.touk.nussknacker.engine.flink.api.process.FlinkLazyParameterFunctionHelper→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.FlinkLazyParameterFunctionHelper→pl.touk.nussknacker.engine.api.LazyParameterpl.touk.nussknacker.engine.flink.api.process.FlinkLazyParameterFunctionHelper→pl.touk.nussknacker.engine.api.ValueWithContextpl.touk.nussknacker.engine.flink.api.process.FlinkSink→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.FlinkSink→pl.touk.nussknacker.engine.api.ValueWithContextpl.touk.nussknacker.engine.flink.api.process.FlinkSource→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.LazyParameterFilterFunction→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.LazyParameterInterpreterFunction→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.LazyParameterInterpreterFunction→pl.touk.nussknacker.engine.api.ToEvaluateFunctionConverterpl.touk.nussknacker.engine.flink.api.process.LazyParameterMapFunction→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.LazyParameterMapFunction→pl.touk.nussknacker.engine.api.ValueWithContextpl.touk.nussknacker.engine.flink.api.process.OneParamLazyParameterFunction→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.flink.api.process.OneParamLazyParameterFunction→pl.touk.nussknacker.engine.api.LazyParameter
- Direction
- pl.touk.nussknacker.engine.flink.api.process uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.flink.api.process, while a change to pl.touk.nussknacker.engine.flink.api.process can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.flink.api.process uses a module listed above it, which is the healthy direction.
19→14 pl.touk.nussknacker.engine.util uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.util uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.util.AdditionalComponentConfigsForRuntimeExtractor→pl.touk.nussknacker.engine.api.component.ComponentAdditionalConfigpl.touk.nussknacker.engine.util.AdditionalComponentConfigsForRuntimeExtractor→pl.touk.nussknacker.engine.api.component.DesignerWideComponentId
- Direction
- pl.touk.nussknacker.engine.util uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.util, while a change to pl.touk.nussknacker.engine.util can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.util uses a module listed above it, which is the healthy direction.
19→15 pl.touk.nussknacker.engine.util uses pl.touk.nussknacker.engine.api✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.engine.util uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.util.LoggingListener→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.util.LoggingListener→pl.touk.nussknacker.engine.api.MetaDatapl.touk.nussknacker.engine.util.LoggingListener→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.util.LoggingListener→pl.touk.nussknacker.engine.api.ProcessListenerpl.touk.nussknacker.engine.util.MetaDataExtractor→pl.touk.nussknacker.engine.api.MetaData
- Direction
- pl.touk.nussknacker.engine.util uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.util, while a change to pl.touk.nussknacker.engine.util can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.util uses a module listed above it, which is the healthy direction.
20→8 pl.touk.nussknacker.ui.security.api uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.ui.security.api uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation.
- The types involved
pl.touk.nussknacker.ui.security.api.AdminUser→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.security.api.AuthenticatedUser→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.security.api.CommonUser→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.security.api.ImpersonatedUserData→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.security.api.RealLoggedUser→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.security.api.RulesSet→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.ui.security.api uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.ui.security.api, while a change to pl.touk.nussknacker.ui.security.api can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.security.api uses a module listed above it, which is the healthy direction.
20→15 pl.touk.nussknacker.ui.security.api uses pl.touk.nussknacker.engine.api✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.security.api uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.ui.security.api.AuthenticationProvider→pl.touk.nussknacker.engine.api.NamedServiceProvider
- Direction
- pl.touk.nussknacker.ui.security.api uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.ui.security.api, while a change to pl.touk.nussknacker.ui.security.api can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.security.api uses a module listed above it, which is the healthy direction.
21→5 pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.graph.expression✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.canonicalgraph uses a type in pl.touk.nussknacker.engine.graph.expression.
- The types involved
pl.touk.nussknacker.engine.canonicalgraph.ExpressionIdWithMetaData→pl.touk.nussknacker.engine.graph.expression.NodeExpressionIdpl.touk.nussknacker.engine.canonicalgraph.ExpressionRewriter→pl.touk.nussknacker.engine.graph.expression.Expression
- Direction
- pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.graph.expression, so a change to pl.touk.nussknacker.engine.graph.expression can break pl.touk.nussknacker.engine.canonicalgraph, while a change to pl.touk.nussknacker.engine.canonicalgraph can't break pl.touk.nussknacker.engine.graph.expression.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.canonicalgraph uses a module listed above it, which is the healthy direction.
21→6 pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.canonicalgraph uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.engine.canonicalgraph.ExpressionIdWithMetaData→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.canonicalgraph.ExpressionRewriter→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.canonicalgraph, while a change to pl.touk.nussknacker.engine.canonicalgraph can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.canonicalgraph uses a module listed above it, which is the healthy direction.
21→7 pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.graph.node✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.canonicalgraph uses a type in pl.touk.nussknacker.engine.graph.node.
- The types involved
pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcessConverter→pl.touk.nussknacker.engine.graph.node.NodeDatapl.touk.nussknacker.engine.canonicalgraph.ExpressionRewriter→pl.touk.nussknacker.engine.graph.node.NodeDatapl.touk.nussknacker.engine.canonicalgraph.canonicalnode→pl.touk.nussknacker.engine.graph.node.NodeData
- Direction
- pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.graph.node, so a change to pl.touk.nussknacker.engine.graph.node can break pl.touk.nussknacker.engine.canonicalgraph, while a change to pl.touk.nussknacker.engine.canonicalgraph can't break pl.touk.nussknacker.engine.graph.node.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.canonicalgraph uses a module listed above it, which is the healthy direction.
21→9 pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.canonicalgraph uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcessConverter→pl.touk.nussknacker.engine.api.process.ProcessName
- Direction
- pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.canonicalgraph, while a change to pl.touk.nussknacker.engine.canonicalgraph can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.canonicalgraph uses a module listed above it, which is the healthy direction.
21→15 pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.api✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.engine.canonicalgraph uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcessConverter→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.canonicalgraph.ExpressionIdWithMetaData→pl.touk.nussknacker.engine.api.MetaDatapl.touk.nussknacker.engine.canonicalgraph.ExpressionRewriter→pl.touk.nussknacker.engine.api.MetaDatapl.touk.nussknacker.engine.canonicalgraph.ExpressionRewriter→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.canonicalgraph.ProcessNodesRewriter→pl.touk.nussknacker.engine.api.MetaData
- Direction
- pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.canonicalgraph, while a change to pl.touk.nussknacker.engine.canonicalgraph can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.canonicalgraph uses a module listed above it, which is the healthy direction.
21→16 pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.api.graph✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.canonicalgraph uses a type in pl.touk.nussknacker.engine.api.graph.
- The types involved
pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcessConverter→pl.touk.nussknacker.engine.api.graph.Edgepl.touk.nussknacker.engine.canonicalgraph.CanonicalProcessConverter→pl.touk.nussknacker.engine.api.graph.ScenarioGraph
- Direction
- pl.touk.nussknacker.engine.canonicalgraph uses pl.touk.nussknacker.engine.api.graph, so a change to pl.touk.nussknacker.engine.api.graph can break pl.touk.nussknacker.engine.canonicalgraph, while a change to pl.touk.nussknacker.engine.canonicalgraph can't break pl.touk.nussknacker.engine.api.graph.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.canonicalgraph uses a module listed above it, which is the healthy direction.
22→9 pl.touk.nussknacker.engine.deployment uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.deployment uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.deployment.FromGraph→pl.touk.nussknacker.engine.api.process.VersionId
- Direction
- pl.touk.nussknacker.engine.deployment uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.deployment, while a change to pl.touk.nussknacker.engine.deployment can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.deployment uses a module listed above it, which is the healthy direction.
22→14 pl.touk.nussknacker.engine.deployment uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.deployment uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.deployment.AdditionalModelConfigs→pl.touk.nussknacker.engine.api.component.ComponentAdditionalConfigpl.touk.nussknacker.engine.deployment.AdditionalModelConfigs→pl.touk.nussknacker.engine.api.component.DesignerWideComponentIdpl.touk.nussknacker.engine.deployment.DeploymentData→pl.touk.nussknacker.engine.api.component.NodesDeploymentData
- Direction
- pl.touk.nussknacker.engine.deployment uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.deployment, while a change to pl.touk.nussknacker.engine.deployment can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.deployment uses a module listed above it, which is the healthy direction.
22→16 pl.touk.nussknacker.engine.deployment uses pl.touk.nussknacker.engine.api.graph✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.deployment uses a type in pl.touk.nussknacker.engine.api.graph.
- The types involved
pl.touk.nussknacker.engine.deployment.FromGraph→pl.touk.nussknacker.engine.api.graph.ScenarioGraph
- Direction
- pl.touk.nussknacker.engine.deployment uses pl.touk.nussknacker.engine.api.graph, so a change to pl.touk.nussknacker.engine.api.graph can break pl.touk.nussknacker.engine.deployment, while a change to pl.touk.nussknacker.engine.deployment can't break pl.touk.nussknacker.engine.api.graph.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.deployment uses a module listed above it, which is the healthy direction.
22→36 pl.touk.nussknacker.engine.deployment uses pl.touk.nussknacker.engine.api.deployment part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.deployment uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.engine.deployment.DeploymentId→pl.touk.nussknacker.engine.api.deployment.ProcessActionId
- Direction
- pl.touk.nussknacker.engine.deployment uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.engine.deployment, while a change to pl.touk.nussknacker.engine.deployment can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→8 pl.touk.nussknacker.engine.kafka uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.kafka uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation.
- The types involved
pl.touk.nussknacker.engine.kafka.CachingKafkaAdminClient→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.engine.kafka uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.engine.kafka, while a change to pl.touk.nussknacker.engine.kafka can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.kafka uses a module listed above it, which is the healthy direction.
23→9 pl.touk.nussknacker.engine.kafka uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.kafka uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.kafka.ConsumerGroupDeterminer→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.kafka.PartitionByKeyFlinkKafkaSink→pl.touk.nussknacker.engine.api.process.Sink
- Direction
- pl.touk.nussknacker.engine.kafka uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.kafka, while a change to pl.touk.nussknacker.engine.kafka can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.kafka uses a module listed above it, which is the healthy direction.
23→15 pl.touk.nussknacker.engine.kafka uses pl.touk.nussknacker.engine.api✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.kafka uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.kafka.ConsumerGroupDeterminer→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.kafka.PartitionByKeyFlinkKafkaSink→pl.touk.nussknacker.engine.api.NodeId
- Direction
- pl.touk.nussknacker.engine.kafka uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.kafka, while a change to pl.touk.nussknacker.engine.kafka can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.kafka uses a module listed above it, which is the healthy direction.
23→18 pl.touk.nussknacker.engine.kafka uses pl.touk.nussknacker.engine.flink.api.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.kafka uses a type in pl.touk.nussknacker.engine.flink.api.process.
- The types involved
pl.touk.nussknacker.engine.kafka.ConsumerGroupDeterminer→pl.touk.nussknacker.engine.flink.api.process.FlinkCustomNodeContext
- Direction
- pl.touk.nussknacker.engine.kafka uses pl.touk.nussknacker.engine.flink.api.process, so a change to pl.touk.nussknacker.engine.flink.api.process can break pl.touk.nussknacker.engine.kafka, while a change to pl.touk.nussknacker.engine.kafka can't break pl.touk.nussknacker.engine.flink.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.kafka uses a module listed above it, which is the healthy direction.
24→2 pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 10 pairs of types, where a type in pl.touk.nussknacker.engine.spel uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.spel.CollectedTypingResult→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.spel.ExpressionSuggestion→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.spel.Parameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.spel.SpelExpressionParser→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.spel.SpelExpressionSuggester→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.spel.SpelExpressionTypingErrorConverter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.spel.SpelExpressionTypingInfo→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.spel.SpelTyper→pl.touk.nussknacker.engine.api.typed.typing.TypedClasspl.touk.nussknacker.engine.spel.SpelTyper→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.spel.SpelTyper→pl.touk.nussknacker.engine.api.typed.typing.Unknown
- Direction
- pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.spel, while a change to pl.touk.nussknacker.engine.spel can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.spel uses a module listed above it, which is the healthy direction.
24→5 pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.graph.expression✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.spel uses a type in pl.touk.nussknacker.engine.graph.expression.
- The types involved
pl.touk.nussknacker.engine.spel.CompiledSpelExpression→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.spel.SpelExpressionRepr→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.spel.SpelExpressionSuggester→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.engine.spel.SpelTyper→pl.touk.nussknacker.engine.graph.expression.Expression
- Direction
- pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.graph.expression, so a change to pl.touk.nussknacker.engine.graph.expression can break pl.touk.nussknacker.engine.spel, while a change to pl.touk.nussknacker.engine.spel can't break pl.touk.nussknacker.engine.graph.expression.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.spel uses a module listed above it, which is the healthy direction.
24→11 pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.spel uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.engine.spel.NuSpelNodeParser→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.spel.SpelExpressionParser→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.spel.SpelExpressionSuggester→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.spel.SpelTyper→pl.touk.nussknacker.engine.api.context.ValidationContext
- Direction
- pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine.spel, while a change to pl.touk.nussknacker.engine.spel can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.spel uses a module listed above it, which is the healthy direction.
24→13 pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.api.definition✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.spel uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.spel.ExpressionSuggestion→pl.touk.nussknacker.engine.api.definition.Parameter
- Direction
- pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.spel, while a change to pl.touk.nussknacker.engine.spel can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.spel uses a module listed above it, which is the healthy direction.
24→15 pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.api✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.spel uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.spel.CompiledSpelExpression→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.spel.CompiledSpelExpression→pl.touk.nussknacker.engine.api.TemplateRenderedPartpl.touk.nussknacker.engine.spel.SpelExpressionRepr→pl.touk.nussknacker.engine.api.Context
- Direction
- pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.spel, while a change to pl.touk.nussknacker.engine.spel can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.spel uses a module listed above it, which is the healthy direction.
24→17 pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.expression.parse✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.spel uses a type in pl.touk.nussknacker.engine.expression.parse.
- The types involved
pl.touk.nussknacker.engine.spel.CompiledSpelExpression→pl.touk.nussknacker.engine.expression.parse.CompiledExpressionpl.touk.nussknacker.engine.spel.SpelExpressionParser→pl.touk.nussknacker.engine.expression.parse.ExpressionParserpl.touk.nussknacker.engine.spel.SpelExpressionParser→pl.touk.nussknacker.engine.expression.parse.TypedExpression
- Direction
- pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.expression.parse, so a change to pl.touk.nussknacker.engine.expression.parse can break pl.touk.nussknacker.engine.spel, while a change to pl.touk.nussknacker.engine.spel can't break pl.touk.nussknacker.engine.expression.parse.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.spel uses a module listed above it, which is the healthy direction.
24→19 pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.util✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.spel uses a type in pl.touk.nussknacker.engine.util.
- The types involved
pl.touk.nussknacker.engine.spel.SpelExpressionSuggester→pl.touk.nussknacker.engine.util.CaretPosition2d
- Direction
- pl.touk.nussknacker.engine.spel uses pl.touk.nussknacker.engine.util, so a change to pl.touk.nussknacker.engine.util can break pl.touk.nussknacker.engine.spel, while a change to pl.touk.nussknacker.engine.spel can't break pl.touk.nussknacker.engine.util.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.spel uses a module listed above it, which is the healthy direction.
25→2 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 7 pairs of types, where a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.ExpressionSuggestionDto→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationRequest→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationResult→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationResultDto→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.ParameterDto→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.ParametersValidationRequest→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.TestCaseAdditionalVariablesResponseDto→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, while a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a module listed above it, which is the healthy direction.
25→3 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.graph.expression.Expression.Language✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a type in pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- The types involved
pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.TypingResultInJson→pl.touk.nussknacker.engine.graph.expression.Expression.Language.Json
- Direction
- pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.graph.expression.Expression.Language, so a change to pl.touk.nussknacker.engine.graph.expression.Expression.Language can break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, while a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can't break pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a module listed above it, which is the healthy direction.
25→5 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.graph.expression✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a type in pl.touk.nussknacker.engine.graph.expression.
- The types involved
pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.ExpressionSuggestionRequestDto→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.GenerateEnricherMockResponseDto→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.TestSourceParameters→pl.touk.nussknacker.engine.graph.expression.Expressionpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.UIValueParameterDto→pl.touk.nussknacker.engine.graph.expression.Expression
- Direction
- pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.graph.expression, so a change to pl.touk.nussknacker.engine.graph.expression can break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, while a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can't break pl.touk.nussknacker.engine.graph.expression.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a module listed above it, which is the healthy direction.
25→6 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeDataSchemas→pl.touk.nussknacker.engine.api.parameter.ParameterValueCompileTimeValidationpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeDataSchemas→pl.touk.nussknacker.engine.api.parameter.ParameterValueInputpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.TestSourceParameters→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, while a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a module listed above it, which is the healthy direction.
25→7 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.graph.node✕
- Connections
- 7 pairs of types, where a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a type in pl.touk.nussknacker.engine.graph.node.
- The types involved
pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeDataSchemas→pl.touk.nussknacker.engine.graph.node.BranchEndDefinitionpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeDataSchemas→pl.touk.nussknacker.engine.graph.node.FragmentOutputVarDefinitionpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeDataSchemas→pl.touk.nussknacker.engine.graph.node.NodeDatapl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeDataSchemas→pl.touk.nussknacker.engine.graph.node.UserDefinedAdditionalNodeFieldspl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationRequest→pl.touk.nussknacker.engine.graph.node.NodeDatapl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationRequestDto→pl.touk.nussknacker.engine.graph.node.NodeDatapl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.RecordsRequestDto→pl.touk.nussknacker.engine.graph.node.NodeData
- Direction
- pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.graph.node, so a change to pl.touk.nussknacker.engine.graph.node can break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, while a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can't break pl.touk.nussknacker.engine.graph.node.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a module listed above it, which is the healthy direction.
25→9 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeDataSchemas→pl.touk.nussknacker.engine.api.process.Sinkpl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeDataSchemas→pl.touk.nussknacker.engine.api.process.Sourcepl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.PropertiesValidationRequestDto→pl.touk.nussknacker.engine.api.process.ProcessName
- Direction
- pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, while a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a module listed above it, which is the healthy direction.
25→15 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeDataSchemas→pl.touk.nussknacker.engine.api.LayoutDatapl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.PropertiesValidationRequestDto→pl.touk.nussknacker.engine.api.ProcessAdditionalFields
- Direction
- pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, while a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a module listed above it, which is the healthy direction.
25→16 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api.graph✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a type in pl.touk.nussknacker.engine.api.graph.
- The types involved
pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.GenerateEnricherMockRequestDto→pl.touk.nussknacker.engine.api.graph.ProcessPropertiespl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationRequest→pl.touk.nussknacker.engine.api.graph.Edgepl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationRequest→pl.touk.nussknacker.engine.api.graph.ProcessPropertiespl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationRequestDto→pl.touk.nussknacker.engine.api.graph.Edgepl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationRequestDto→pl.touk.nussknacker.engine.api.graph.ProcessPropertiespl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.RecordsRequestDto→pl.touk.nussknacker.engine.api.graph.ProcessProperties
- Direction
- pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.api.graph, so a change to pl.touk.nussknacker.engine.api.graph can break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, while a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can't break pl.touk.nussknacker.engine.api.graph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a module listed above it, which is the healthy direction.
25→19 pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.util✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a type in pl.touk.nussknacker.engine.util.
- The types involved
pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.ExpressionSuggestionRequestDto→pl.touk.nussknacker.engine.util.CaretPosition2d
- Direction
- pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses pl.touk.nussknacker.engine.util, so a change to pl.touk.nussknacker.engine.util can break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, while a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can't break pl.touk.nussknacker.engine.util.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos uses a module listed above it, which is the healthy direction.
26→2 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.compile.CompilationResult→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→6 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.engine.compile.CompileTimeParameterValidation→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.compile.NodeParametersAdjuster→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→7 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.graph.node✕
- Connections
- 9 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.graph.node.
- The types involved
pl.touk.nussknacker.engine.compile.NameValidator→pl.touk.nussknacker.engine.graph.node.NodeDatapl.touk.nussknacker.engine.compile.PartSubGraphCompiler→pl.touk.nussknacker.engine.graph.node.EndingNodeDatapl.touk.nussknacker.engine.compile.PartSubGraphCompiler→pl.touk.nussknacker.engine.graph.node.Nodepl.touk.nussknacker.engine.compile.PartSubGraphCompiler→pl.touk.nussknacker.engine.graph.node.OneOutputSubsequentNodeDatapl.touk.nussknacker.engine.compile.PartSubGraphCompiler→pl.touk.nussknacker.engine.graph.node.StartingNodeDatapl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.graph.node.BranchEndDefinitionpl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.graph.node.CustomNodeDatapl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.graph.node.EndingNodepl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.graph.node.SourceNodeData
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.graph.node, so a change to pl.touk.nussknacker.engine.graph.node can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.graph.node.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→8 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation.
- The types involved
pl.touk.nussknacker.engine.compile.NameValidator→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→9 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.compile.FragmentSourceWithTestWithParametersSupportFactory→pl.touk.nussknacker.engine.api.process.Sourcepl.touk.nussknacker.engine.compile.NameValidator→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.compile.PartSubGraphCompiler→pl.touk.nussknacker.engine.api.process.Sourcepl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.api.process.Sink
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→10 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.context.ProcessCompilationError✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.api.context.ProcessCompilationError.
- The types involved
pl.touk.nussknacker.engine.compile.NameValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError.IdErrorType
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.context.ProcessCompilationError, so a change to pl.touk.nussknacker.engine.api.context.ProcessCompilationError can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.api.context.ProcessCompilationError.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→11 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 10 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.engine.compile.CompilationResult→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.CompileTimeParameterValidation→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.compile.ComponentExecutorFactory→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.FragmentValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.NameValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.NodeTypingInfo→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.compile.NodeValidationExceptionHandler→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.compile.ProcessValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→13 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.definition✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.compile.CompilationResult→pl.touk.nussknacker.engine.api.definition.Parameterpl.touk.nussknacker.engine.compile.CompileTimeParameterValidation→pl.touk.nussknacker.engine.api.definition.Validatorpl.touk.nussknacker.engine.compile.NodeTypingInfo→pl.touk.nussknacker.engine.api.definition.Parameter
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→14 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.api.component.ComponentOutputpl.touk.nussknacker.engine.compile.ProcessCompilerData→pl.touk.nussknacker.engine.api.component.NodesDeploymentData
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→15 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api✕
- Connections
- 13 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.compile.CompileTimeParameterValidation→pl.touk.nussknacker.engine.api.BranchEagerParameterEvaluationResultpl.touk.nussknacker.engine.compile.CompileTimeParameterValidation→pl.touk.nussknacker.engine.api.EagerParameterEvaluationResultpl.touk.nussknacker.engine.compile.CompileTimeParameterValidation→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.compile.CompileTimeParameterValidation→pl.touk.nussknacker.engine.api.SingleEagerParameterEvaluationResultpl.touk.nussknacker.engine.compile.NodeParametersAdjuster→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.compile.NodeParametersAdjuster→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.compile.NodeValidationExceptionHandler→pl.touk.nussknacker.engine.api.MetaDatapl.touk.nussknacker.engine.compile.NodeValidationExceptionHandler→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.compile.NodeValidationExceptionHandler→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.compile.ProcessCompilerData→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.compile.ProcessCompilerData→pl.touk.nussknacker.engine.api.ProcessListener
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→17 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.expression.parse✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.expression.parse.
- The types involved
pl.touk.nussknacker.engine.compile.CompileTimeParameterValidation→pl.touk.nussknacker.engine.expression.parse.MultipleBranchesTypedValuepl.touk.nussknacker.engine.compile.CompileTimeParameterValidation→pl.touk.nussknacker.engine.expression.parse.SingleBranchTypedValue
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.expression.parse, so a change to pl.touk.nussknacker.engine.expression.parse can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.expression.parse.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→21 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.canonicalgraph✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.canonicalgraph.
- The types involved
pl.touk.nussknacker.engine.compile.FragmentResolver→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.engine.compile.FragmentValidator→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.engine.compile.NameValidator→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.engine.compile.ProcessCompiler→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.engine.compile.ProcessValidator→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcess
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.canonicalgraph, so a change to pl.touk.nussknacker.engine.canonicalgraph can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.canonicalgraph.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile uses a module listed above it, which is the healthy direction.
26→28 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.compile.nodecompilation part of a loop✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.compile.nodecompilation.
- The types involved
pl.touk.nussknacker.engine.compile.PartSubGraphCompiler→pl.touk.nussknacker.engine.compile.nodecompilation.SingleInputNodeInputValidationContextpl.touk.nussknacker.engine.compile.ProcessCompiler→pl.touk.nussknacker.engine.compile.nodecompilation.NodeCompilerpl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.compile.nodecompilation.NodeCompilerpl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.compile.nodecompilation.NodeInputValidationContextpl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.compile.nodecompilation.SingleInputNodeInputValidationContextpl.touk.nussknacker.engine.compile.ProcessCompilerData→pl.touk.nussknacker.engine.compile.nodecompilation.LazyParameterCreationStrategy
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine.compile.nodecompilation, so a change to pl.touk.nussknacker.engine.compile.nodecompilation can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.compile.nodecompilation.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→37 pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine part of a loop✕
- Connections
- 9 pairs of types, where a type in pl.touk.nussknacker.engine.compile uses a type in pl.touk.nussknacker.engine.
- The types involved
pl.touk.nussknacker.engine.compile.ExpressionCompiler→pl.touk.nussknacker.engine.ModelDatapl.touk.nussknacker.engine.compile.PartSubGraphCompiler→pl.touk.nussknacker.engine.ScenarioCompilationDependenciespl.touk.nussknacker.engine.compile.ProcessCompiler→pl.touk.nussknacker.engine.CustomProcessValidatorpl.touk.nussknacker.engine.compile.ProcessCompiler→pl.touk.nussknacker.engine.ScenarioCompilationDependenciespl.touk.nussknacker.engine.compile.ProcessCompilerBase→pl.touk.nussknacker.engine.ScenarioCompilationDependenciespl.touk.nussknacker.engine.compile.ProcessCompilerData→pl.touk.nussknacker.engine.CustomProcessValidatorpl.touk.nussknacker.engine.compile.ProcessCompilerData→pl.touk.nussknacker.engine.RuntimeModepl.touk.nussknacker.engine.compile.ProcessValidator→pl.touk.nussknacker.engine.CustomProcessValidatorpl.touk.nussknacker.engine.compile.ProcessValidator→pl.touk.nussknacker.engine.ScenarioCompilationDependencies
- Direction
- pl.touk.nussknacker.engine.compile uses pl.touk.nussknacker.engine, so a change to pl.touk.nussknacker.engine can break pl.touk.nussknacker.engine.compile, while a change to pl.touk.nussknacker.engine.compile can't break pl.touk.nussknacker.engine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→9 pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 22 pairs of types, where a type in pl.touk.nussknacker.ui.db.entity uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.ui.db.entity.AttachmentEntityData→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.AttachmentEntityData→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.db.entity.BaseEntityFactory→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.BaseEntityFactory→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.db.entity.BaseEntityFactory→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.db.entity.LiveDataEntityData→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessEntity→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessEntity→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.db.entity.PeriodicProcessEntity→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithDeploymentDetails→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithDeploymentDetails→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithDeploymentDetails→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithoutDeploymentDetails→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithoutDeploymentDetails→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithoutDeploymentDetails→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.db.entity.ProcessEntityData→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.ProcessEntityData→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.db.entity.ProcessVersionEntityData→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.ProcessVersionEntityData→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.db.entity.ScenarioActivityEntityData→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.ScenarioLabelEntityData→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.db.entity.TagsEntityData→pl.touk.nussknacker.engine.api.process.ProcessId
- Direction
- pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.ui.db.entity, while a change to pl.touk.nussknacker.ui.db.entity can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.db.entity uses a module listed above it, which is the healthy direction.
27→14 pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.db.entity uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.ui.db.entity.ComponentUsages→pl.touk.nussknacker.engine.api.component.ComponentTypepl.touk.nussknacker.ui.db.entity.LegacyComponentUsages→pl.touk.nussknacker.engine.api.component.ComponentType
- Direction
- pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.ui.db.entity, while a change to pl.touk.nussknacker.ui.db.entity can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.db.entity uses a module listed above it, which is the healthy direction.
27→15 pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.api✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.db.entity uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.ui.db.entity.LegacyComponentUsages→pl.touk.nussknacker.engine.api.NodeId
- Direction
- pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.ui.db.entity, while a change to pl.touk.nussknacker.ui.db.entity can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.db.entity uses a module listed above it, which is the healthy direction.
27→21 pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.canonicalgraph✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.ui.db.entity uses a type in pl.touk.nussknacker.engine.canonicalgraph.
- The types involved
pl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithDeploymentDetails→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.ui.db.entity.PeriodicProcessesTableFactory→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.ui.db.entity.ProcessVersionEntityData→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcess
- Direction
- pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.canonicalgraph, so a change to pl.touk.nussknacker.engine.canonicalgraph can break pl.touk.nussknacker.ui.db.entity, while a change to pl.touk.nussknacker.ui.db.entity can't break pl.touk.nussknacker.engine.canonicalgraph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.db.entity uses a module listed above it, which is the healthy direction.
27→22 pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.deployment✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.db.entity uses a type in pl.touk.nussknacker.engine.deployment.
- The types involved
pl.touk.nussknacker.ui.db.entity.BaseEntityFactory→pl.touk.nussknacker.engine.deployment.DeploymentId
- Direction
- pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.deployment, so a change to pl.touk.nussknacker.engine.deployment can break pl.touk.nussknacker.ui.db.entity, while a change to pl.touk.nussknacker.ui.db.entity can't break pl.touk.nussknacker.engine.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.db.entity uses a module listed above it, which is the healthy direction.
27→36 pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.api.deployment part of a loop✕
- Connections
- 15 pairs of types, where a type in pl.touk.nussknacker.ui.db.entity uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.ui.db.entity.BaseEntityFactory→pl.touk.nussknacker.engine.api.deployment.DeploymentStatusNamepl.touk.nussknacker.ui.db.entity.BaseEntityFactory→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.db.entity.BaseEntityFactory→pl.touk.nussknacker.engine.api.deployment.ProcessActionStatepl.touk.nussknacker.ui.db.entity.BaseEntityFactory→pl.touk.nussknacker.engine.api.deployment.ScenarioActionNamepl.touk.nussknacker.ui.db.entity.BaseEntityFactory→pl.touk.nussknacker.engine.api.deployment.ScenarioActivityIdpl.touk.nussknacker.ui.db.entity.LiveDataEntityData→pl.touk.nussknacker.engine.api.deployment.ScenarioActivityIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessEntity→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithDeploymentDetails→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithoutDeploymentDetails→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.db.entity.PeriodicProcessesTableFactory→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.db.entity.ScenarioActivityEntityData→pl.touk.nussknacker.engine.api.deployment.ProcessActionStatepl.touk.nussknacker.ui.db.entity.ScenarioActivityEntityData→pl.touk.nussknacker.engine.api.deployment.ScenarioActivityIdpl.touk.nussknacker.ui.db.entity.ScenarioActivityEntityData→pl.touk.nussknacker.engine.api.deployment.ScenarioVersionIdpl.touk.nussknacker.ui.db.entity.ScenarioActivityEntityFactory→pl.touk.nussknacker.engine.api.deployment.ScenarioIdpl.touk.nussknacker.ui.db.entity.ScenarioActivityEntityFactory→pl.touk.nussknacker.engine.api.deployment.ScenarioVersionId
- Direction
- pl.touk.nussknacker.ui.db.entity uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.ui.db.entity, while a change to pl.touk.nussknacker.ui.db.entity can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→2 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 8 pairs of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.BuiltInNodeCompiler→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.compile.nodecompilation.EvaluableLazyParameter→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.compile.nodecompilation.EvaluableLazyParameterCreator→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.compile.nodecompilation.MultipleInputBranchesNodeInputValidationContext→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.compile.nodecompilation.NodeInputValidationContext→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.compile.nodecompilation.SingleInputNodeInputValidationContext→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.compile.nodecompilation.StaticComponentOutputValidationContextDeterminer→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.compile.nodecompilation.ValidationPerformed→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→5 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.graph.expression✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.graph.expression.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.BuiltInNodeCompiler→pl.touk.nussknacker.engine.graph.expression.Expression
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.graph.expression, so a change to pl.touk.nussknacker.engine.graph.expression can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.graph.expression.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→6 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 7 pairs of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.BaseComponentValidationHelper→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.compile.nodecompilation.BuiltInNodeCompiler→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.compile.nodecompilation.DynamicNodeValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.compile.nodecompilation.NodeCompiler→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.compile.nodecompilation.TransformationResult→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.compile.nodecompilation.ValueEditorValidator→pl.touk.nussknacker.engine.api.parameter.ParameterNamepl.touk.nussknacker.engine.compile.nodecompilation.ValueEditorValidator→pl.touk.nussknacker.engine.api.parameter.ParameterValueInput
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→7 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.graph.node✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.graph.node.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.StaticComponentOutputValidationContextDeterminer→pl.touk.nussknacker.engine.graph.node.CustomNodeDatapl.touk.nussknacker.engine.compile.nodecompilation.StaticComponentOutputValidationContextDeterminer→pl.touk.nussknacker.engine.graph.node.NodeData
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.graph.node, so a change to pl.touk.nussknacker.engine.graph.node can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.graph.node.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→8 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.ValueEditorValidator→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→9 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.MethodBasedServiceInvoker→pl.touk.nussknacker.engine.api.process.ComponentUseContext
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→11 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 16 pairs of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.BaseComponentValidationHelper→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.compile.nodecompilation.BaseComponentValidationHelper→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.nodecompilation.BuiltInNodeCompiler→pl.touk.nussknacker.engine.api.context.OutputVarpl.touk.nussknacker.engine.compile.nodecompilation.BuiltInNodeCompiler→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.compile.nodecompilation.DynamicNodeValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.nodecompilation.MultipleInputBranchesNodeInputValidationContext→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.compile.nodecompilation.RecordValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationErrorpl.touk.nussknacker.engine.compile.nodecompilation.RecordValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.nodecompilation.SingleInputNodeInputValidationContext→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.compile.nodecompilation.StaticComponentOutputValidationContextDeterminer→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.nodecompilation.StaticComponentOutputValidationContextDeterminer→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.compile.nodecompilation.TransformationResult→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.nodecompilation.TransformationResult→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.compile.nodecompilation.ValidationPerformed→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.engine.compile.nodecompilation.ValidationPerformed→pl.touk.nussknacker.engine.api.context.ValidationContextpl.touk.nussknacker.engine.compile.nodecompilation.ValueEditorValidator→pl.touk.nussknacker.engine.api.context.PartSubGraphCompilationError
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→12 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.context.transformation✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.api.context.transformation.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.DynamicNodeValidator→pl.touk.nussknacker.engine.api.context.transformation.DynamicComponent
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.context.transformation, so a change to pl.touk.nussknacker.engine.api.context.transformation can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.api.context.transformation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→13 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.definition✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.BaseComponentValidationHelper→pl.touk.nussknacker.engine.api.definition.ParameterValidatorpl.touk.nussknacker.engine.compile.nodecompilation.StaticComponentOutputValidationContextDeterminer→pl.touk.nussknacker.engine.api.definition.Parameterpl.touk.nussknacker.engine.compile.nodecompilation.TransformationResult→pl.touk.nussknacker.engine.api.definition.Parameterpl.touk.nussknacker.engine.compile.nodecompilation.ValidationPerformed→pl.touk.nussknacker.engine.api.definition.Parameterpl.touk.nussknacker.engine.compile.nodecompilation.ValueEditorValidator→pl.touk.nussknacker.engine.api.definition.FixedExpressionValuepl.touk.nussknacker.engine.compile.nodecompilation.ValueEditorValidator→pl.touk.nussknacker.engine.api.definition.ParameterEditor
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→14 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.DynamicNodeValidator→pl.touk.nussknacker.engine.api.component.ParameterConfig
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→15 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api✕
- Connections
- 17 pairs of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.BaseComponentValidationHelper→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.compile.nodecompilation.BuiltInNodeCompiler→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.compile.nodecompilation.DefaultToEvaluateFunctionConverter→pl.touk.nussknacker.engine.api.LazyParameterpl.touk.nussknacker.engine.compile.nodecompilation.DefaultToEvaluateFunctionConverter→pl.touk.nussknacker.engine.api.ToEvaluateFunctionConverterpl.touk.nussknacker.engine.compile.nodecompilation.EvaluableLazyParameter→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.compile.nodecompilation.EvaluableLazyParameter→pl.touk.nussknacker.engine.api.LazyParameterpl.touk.nussknacker.engine.compile.nodecompilation.EvaluableLazyParameter→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.compile.nodecompilation.EvaluableLazyParameterCreatorDeps→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.compile.nodecompilation.MethodBasedServiceInvoker→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.compile.nodecompilation.MethodBasedServiceInvoker→pl.touk.nussknacker.engine.api.ServiceInvokerpl.touk.nussknacker.engine.compile.nodecompilation.ParameterEvaluator→pl.touk.nussknacker.engine.api.ProcessListenerpl.touk.nussknacker.engine.compile.nodecompilation.RecordValidator→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.compile.nodecompilation.StaticComponentOutputValidationContextDeterminer→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.compile.nodecompilation.StaticComponentOutputValidationContextDeterminer→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.compile.nodecompilation.StaticComponentOutputValidationContextDeterminer→pl.touk.nussknacker.engine.api.NodeNamepl.touk.nussknacker.engine.compile.nodecompilation.TransformationResult→pl.touk.nussknacker.engine.api.EagerParameterEvaluationResultpl.touk.nussknacker.engine.compile.nodecompilation.ValueEditorValidator→pl.touk.nussknacker.engine.api.NodeId
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→17 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.expression.parse✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.expression.parse.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.BaseComponentValidationHelper→pl.touk.nussknacker.engine.expression.parse.TypedExpressionpl.touk.nussknacker.engine.compile.nodecompilation.BuiltInNodeCompiler→pl.touk.nussknacker.engine.expression.parse.CompiledExpressionpl.touk.nussknacker.engine.compile.nodecompilation.CompiledIndexedRecordField→pl.touk.nussknacker.engine.expression.parse.TypedExpression
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.expression.parse, so a change to pl.touk.nussknacker.engine.expression.parse can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.expression.parse.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→26 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.compile✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.compile.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.EvaluableLazyParameterCreatorDeps→pl.touk.nussknacker.engine.compile.ExpressionCompilerpl.touk.nussknacker.engine.compile.nodecompilation.NodeCompiler→pl.touk.nussknacker.engine.compile.ExpressionCompilerpl.touk.nussknacker.engine.compile.nodecompilation.ParameterEvaluator→pl.touk.nussknacker.engine.compile.ExpressionCompiler
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.compile, so a change to pl.touk.nussknacker.engine.compile can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.compile.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.compile.nodecompilation uses a module listed above it, which is the healthy direction.
28→30 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.definition.component part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.definition.component.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.DynamicNodeValidator→pl.touk.nussknacker.engine.definition.component.NodeCompilationDependencies
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine.definition.component, so a change to pl.touk.nussknacker.engine.definition.component can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.definition.component.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→37 pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.compile.nodecompilation uses a type in pl.touk.nussknacker.engine.
- The types involved
pl.touk.nussknacker.engine.compile.nodecompilation.NodeCompiler→pl.touk.nussknacker.engine.ModelData
- Direction
- pl.touk.nussknacker.engine.compile.nodecompilation uses pl.touk.nussknacker.engine, so a change to pl.touk.nussknacker.engine can break pl.touk.nussknacker.engine.compile.nodecompilation, while a change to pl.touk.nussknacker.engine.compile.nodecompilation can't break pl.touk.nussknacker.engine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→8 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation.
- The types involved
pl.touk.nussknacker.ui.process.repository.DbScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.process.repository.ProcessDBQueryRepository→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.process.repository.ScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.process.repository.ScenarioActionRepositoryAuditLogDecorator→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.process.repository.SlickPeriodicProcessesRepository→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.repository uses a module listed above it, which is the healthy direction.
29→9 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 32 pairs of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.engine.api.process. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
pl.touk.nussknacker.ui.process.repository.DBProcessRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.DBProcessRepository→pl.touk.nussknacker.engine.api.process.ProcessIdWithNamepl.touk.nussknacker.ui.process.repository.DBProcessRepository→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.repository.DBProcessRepository→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.repository.DbScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.DbScenarioActionRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.DbScenarioActionRepository→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.repository.FetchingProcessRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.FetchingProcessRepository→pl.touk.nussknacker.engine.api.process.ProcessIdWithNamepl.touk.nussknacker.ui.process.repository.FetchingProcessRepository→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.repository.FetchingProcessRepository→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.repository.ProcessDBQueryRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.ProcessDBQueryRepository→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.repository.PullProcessRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.PullProcessRepository→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.repository.PullProcessRepository→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.repository.ScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.ScenarioActionRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.ScenarioActionRepository→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.repository.ScenarioActionRepositoryAuditLogDecorator→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.ScenarioActionRepositoryAuditLogDecorator→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.repository.ScenarioIdData→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.ScenarioIdData→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.repository.ScenarioLabelsRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.repository.ScenarioMetadataRepository→pl.touk.nussknacker.engine.api.process.ProcessName
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.repository uses a module listed above it, which is the healthy direction.
29→15 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.api✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.ui.process.repository.DbScenarioActionRepository→pl.touk.nussknacker.engine.api.Commentpl.touk.nussknacker.ui.process.repository.DeploymentComment→pl.touk.nussknacker.engine.api.Commentpl.touk.nussknacker.ui.process.repository.FetchingProcessRepository→pl.touk.nussknacker.engine.api.ProcessVersionpl.touk.nussknacker.ui.process.repository.ScenarioActionRepository→pl.touk.nussknacker.engine.api.Commentpl.touk.nussknacker.ui.process.repository.ScenarioActionRepositoryAuditLogDecorator→pl.touk.nussknacker.engine.api.Commentpl.touk.nussknacker.ui.process.repository.SlickPeriodicProcessesRepository→pl.touk.nussknacker.engine.api.ProcessVersion
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.repository uses a module listed above it, which is the healthy direction.
29→16 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.api.graph✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.engine.api.graph.
- The types involved
pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntity→pl.touk.nussknacker.engine.api.graph.ScenarioGraph
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.api.graph, so a change to pl.touk.nussknacker.engine.api.graph can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.engine.api.graph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.repository uses a module listed above it, which is the healthy direction.
29→20 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.ui.security.api✕
- Connections
- 11 pairs of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.ui.security.api.
- The types involved
pl.touk.nussknacker.ui.process.repository.DBProcessRepository→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.repository.DbScenarioActionReadOnlyRepository→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.repository.DbScenarioActionRepository→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.repository.FetchingProcessRepository→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.repository.ProcessDBQueryRepository→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.repository.PullProcessRepository→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.repository.ScenarioActionReadOnlyRepository→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.repository.ScenarioActionRepository→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.repository.ScenarioActionRepositoryAuditLogDecorator→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.repository.ScenarioLabelsRepository→pl.touk.nussknacker.ui.security.api.CommonUserpl.touk.nussknacker.ui.process.repository.ScenarioLabelsRepository→pl.touk.nussknacker.ui.security.api.LoggedUser
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.ui.security.api, so a change to pl.touk.nussknacker.ui.security.api can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.ui.security.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.repository uses a module listed above it, which is the healthy direction.
29→21 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.canonicalgraph✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.engine.canonicalgraph.
- The types involved
pl.touk.nussknacker.ui.process.repository.DBProcessRepository→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.ui.process.repository.FetchingProcessRepository→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.ui.process.repository.ScenarioComponentsUsagesHelper→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.ui.process.repository.SlickPeriodicProcessesRepository→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcess
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.canonicalgraph, so a change to pl.touk.nussknacker.engine.canonicalgraph can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.engine.canonicalgraph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.repository uses a module listed above it, which is the healthy direction.
29→27 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.ui.db.entity✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.ui.db.entity.
- The types involved
pl.touk.nussknacker.ui.process.repository.ProcessDBQueryRepository→pl.touk.nussknacker.ui.db.entity.ProcessEntityDatapl.touk.nussknacker.ui.process.repository.ProcessDBQueryRepository→pl.touk.nussknacker.ui.db.entity.ProcessEntityFactorypl.touk.nussknacker.ui.process.repository.ScenarioLabelsRepository→pl.touk.nussknacker.ui.db.entity.ScenarioLabelEntityDatapl.touk.nussknacker.ui.process.repository.SlickPeriodicProcessesRepository→pl.touk.nussknacker.ui.db.entity.PeriodicProcessDeploymentsTableFactorypl.touk.nussknacker.ui.process.repository.SlickPeriodicProcessesRepository→pl.touk.nussknacker.ui.db.entity.PeriodicProcessEntityWithoutDeploymentDetailspl.touk.nussknacker.ui.process.repository.SlickPeriodicProcessesRepository→pl.touk.nussknacker.ui.db.entity.PeriodicProcessesTableFactory
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.ui.db.entity, so a change to pl.touk.nussknacker.ui.db.entity can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.ui.db.entity.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.repository uses a module listed above it, which is the healthy direction.
29→31 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.ui.process part of a loop✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.ui.process.
- The types involved
pl.touk.nussknacker.ui.process.repository.FetchingProcessRepository→pl.touk.nussknacker.ui.process.ScenarioQuerypl.touk.nussknacker.ui.process.repository.FetchingProcessRepository→pl.touk.nussknacker.ui.process.ScenarioVersionQuerypl.touk.nussknacker.ui.process.repository.ScenarioMetadataRepository→pl.touk.nussknacker.ui.process.ScenarioMetadata
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.ui.process, so a change to pl.touk.nussknacker.ui.process can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.ui.process.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→33 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.ui.api part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.ui.api.
- The types involved
pl.touk.nussknacker.ui.process.repository.DeploymentComment→pl.touk.nussknacker.ui.api.DeploymentCommentSettings
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.ui.api, so a change to pl.touk.nussknacker.ui.api can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.ui.api.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→36 pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.api.deployment part of a loop✕
- Connections
- 22 pairs of types, where a type in pl.touk.nussknacker.ui.process.repository uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.ui.process.repository.DbScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionpl.touk.nussknacker.ui.process.repository.DbScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.process.repository.DbScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionStatepl.touk.nussknacker.ui.process.repository.DbScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.deployment.ScenarioActionNamepl.touk.nussknacker.ui.process.repository.DbScenarioActionRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionpl.touk.nussknacker.ui.process.repository.DbScenarioActionRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.process.repository.DbScenarioActionRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionStatepl.touk.nussknacker.ui.process.repository.DbScenarioActionRepository→pl.touk.nussknacker.engine.api.deployment.ScenarioActionNamepl.touk.nussknacker.ui.process.repository.ScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionpl.touk.nussknacker.ui.process.repository.ScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.process.repository.ScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionStatepl.touk.nussknacker.ui.process.repository.ScenarioActionReadOnlyRepository→pl.touk.nussknacker.engine.api.deployment.ScenarioActionNamepl.touk.nussknacker.ui.process.repository.ScenarioActionRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionpl.touk.nussknacker.ui.process.repository.ScenarioActionRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.process.repository.ScenarioActionRepository→pl.touk.nussknacker.engine.api.deployment.ScenarioActionNamepl.touk.nussknacker.ui.process.repository.ScenarioActionRepositoryAuditLogDecorator→pl.touk.nussknacker.engine.api.deployment.ProcessActionpl.touk.nussknacker.ui.process.repository.ScenarioActionRepositoryAuditLogDecorator→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.process.repository.ScenarioActionRepositoryAuditLogDecorator→pl.touk.nussknacker.engine.api.deployment.ProcessActionStatepl.touk.nussknacker.ui.process.repository.ScenarioActionRepositoryAuditLogDecorator→pl.touk.nussknacker.engine.api.deployment.ScenarioActionNamepl.touk.nussknacker.ui.process.repository.ScenarioVersionMetadata→pl.touk.nussknacker.engine.api.deployment.UserNamepl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntity→pl.touk.nussknacker.engine.api.deployment.ProcessActionpl.touk.nussknacker.ui.process.repository.SlickPeriodicProcessesRepository→pl.touk.nussknacker.engine.api.deployment.ProcessActionId
- Direction
- pl.touk.nussknacker.ui.process.repository uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.ui.process.repository, while a change to pl.touk.nussknacker.ui.process.repository can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→2 pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.definition.component uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.engine.definition.component.ComponentDefinitionWithImplementation→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.definition.component.ComponentStaticDefinition→pl.touk.nussknacker.engine.api.typed.typing.TypingResultpl.touk.nussknacker.engine.definition.component.ObjectOperatingOnTypes→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.engine.definition.component, while a change to pl.touk.nussknacker.engine.definition.component can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.definition.component uses a module listed above it, which is the healthy direction.
30→6 pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.definition.component uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.engine.definition.component.ComponentAdditionalConfigConverter→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.definition.component, while a change to pl.touk.nussknacker.engine.definition.component can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.definition.component uses a module listed above it, which is the healthy direction.
30→7 pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.graph.node✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.definition.component uses a type in pl.touk.nussknacker.engine.graph.node.
- The types involved
pl.touk.nussknacker.engine.definition.component.NodeCompilationDependencies→pl.touk.nussknacker.engine.graph.node.NodeData
- Direction
- pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.graph.node, so a change to pl.touk.nussknacker.engine.graph.node can break pl.touk.nussknacker.engine.definition.component, while a change to pl.touk.nussknacker.engine.definition.component can't break pl.touk.nussknacker.engine.graph.node.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.definition.component uses a module listed above it, which is the healthy direction.
30→9 pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.definition.component uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.definition.component.NodeCompilationDependencies→pl.touk.nussknacker.engine.api.process.ComponentUseContext
- Direction
- pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.definition.component, while a change to pl.touk.nussknacker.engine.definition.component can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.definition.component uses a module listed above it, which is the healthy direction.
30→13 pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.definition✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine.definition.component uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.definition.component.ComponentStaticDefinition→pl.touk.nussknacker.engine.api.definition.Parameterpl.touk.nussknacker.engine.definition.component.DynamicComponentStaticDefinitionDeterminer→pl.touk.nussknacker.engine.api.definition.Parameterpl.touk.nussknacker.engine.definition.component.NodeCompilationDependencies→pl.touk.nussknacker.engine.api.definition.EngineScenarioCompilationDependencies
- Direction
- pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.definition.component, while a change to pl.touk.nussknacker.engine.definition.component can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.definition.component uses a module listed above it, which is the healthy direction.
30→14 pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 24 pairs of types, where a type in pl.touk.nussknacker.engine.definition.component uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.definition.component.BuiltInComponentSpecificData→pl.touk.nussknacker.engine.api.component.ComponentTypepl.touk.nussknacker.engine.definition.component.ComponentAdditionalConfigConverter→pl.touk.nussknacker.engine.api.component.ComponentAdditionalConfigpl.touk.nussknacker.engine.definition.component.ComponentAdditionalConfigConverter→pl.touk.nussknacker.engine.api.component.ComponentConfigpl.touk.nussknacker.engine.definition.component.ComponentAdditionalConfigConverter→pl.touk.nussknacker.engine.api.component.ParameterAdditionalUIConfigpl.touk.nussknacker.engine.definition.component.ComponentAdditionalConfigConverter→pl.touk.nussknacker.engine.api.component.ParameterConfigpl.touk.nussknacker.engine.definition.component.ComponentDefinitionExtractor→pl.touk.nussknacker.engine.api.component.Componentpl.touk.nussknacker.engine.definition.component.ComponentDefinitionExtractor→pl.touk.nussknacker.engine.api.component.ComponentAdditionalConfigpl.touk.nussknacker.engine.definition.component.ComponentDefinitionExtractor→pl.touk.nussknacker.engine.api.component.ComponentConfigpl.touk.nussknacker.engine.definition.component.ComponentDefinitionExtractor→pl.touk.nussknacker.engine.api.component.ComponentDefinitionpl.touk.nussknacker.engine.definition.component.ComponentDefinitionExtractor→pl.touk.nussknacker.engine.api.component.ComponentGroupNamepl.touk.nussknacker.engine.definition.component.ComponentDefinitionExtractor→pl.touk.nussknacker.engine.api.component.ComponentIdpl.touk.nussknacker.engine.definition.component.ComponentDefinitionExtractor→pl.touk.nussknacker.engine.api.component.DesignerWideComponentIdpl.touk.nussknacker.engine.definition.component.ComponentDefinitionWithImplementation→pl.touk.nussknacker.engine.api.component.Componentpl.touk.nussknacker.engine.definition.component.ComponentDefinitionWithImplementation→pl.touk.nussknacker.engine.api.component.ComponentGroupNamepl.touk.nussknacker.engine.definition.component.ComponentDefinitionWithImplementation→pl.touk.nussknacker.engine.api.component.ComponentIdpl.touk.nussknacker.engine.definition.component.ComponentDefinitionWithImplementation→pl.touk.nussknacker.engine.api.component.ComponentTypepl.touk.nussknacker.engine.definition.component.ComponentDefinitionWithImplementation→pl.touk.nussknacker.engine.api.component.DesignerWideComponentIdpl.touk.nussknacker.engine.definition.component.ComponentTypeSpecificData→pl.touk.nussknacker.engine.api.component.ComponentTypepl.touk.nussknacker.engine.definition.component.ComponentUiDefinition→pl.touk.nussknacker.engine.api.component.ComponentGroupNamepl.touk.nussknacker.engine.definition.component.ComponentUiDefinition→pl.touk.nussknacker.engine.api.component.DesignerWideComponentIdpl.touk.nussknacker.engine.definition.component.FragmentSpecificData→pl.touk.nussknacker.engine.api.component.ComponentTypepl.touk.nussknacker.engine.definition.component.ServiceSpecificData→pl.touk.nussknacker.engine.api.component.ComponentTypepl.touk.nussknacker.engine.definition.component.SinkSpecificData→pl.touk.nussknacker.engine.api.component.ComponentTypepl.touk.nussknacker.engine.definition.component.SourceSpecificData→pl.touk.nussknacker.engine.api.component.ComponentType
- Direction
- pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.definition.component, while a change to pl.touk.nussknacker.engine.definition.component can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.definition.component uses a module listed above it, which is the healthy direction.
30→15 pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.engine.definition.component uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.definition.component.ComponentImplementationInvoker→pl.touk.nussknacker.engine.api.Paramspl.touk.nussknacker.engine.definition.component.NodeCompilationDependencies→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.definition.component.NodeCompilationDependencies→pl.touk.nussknacker.engine.api.MetaDatapl.touk.nussknacker.engine.definition.component.NodeCompilationDependencies→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.definition.component.NodeCompilationDependencies→pl.touk.nussknacker.engine.api.NodeName
- Direction
- pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.definition.component, while a change to pl.touk.nussknacker.engine.definition.component can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.definition.component uses a module listed above it, which is the healthy direction.
30→28 pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.compile.nodecompilation✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.definition.component uses a type in pl.touk.nussknacker.engine.compile.nodecompilation.
- The types involved
pl.touk.nussknacker.engine.definition.component.NodeCompilationDependencies→pl.touk.nussknacker.engine.compile.nodecompilation.NodeInputValidationContext
- Direction
- pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine.compile.nodecompilation, so a change to pl.touk.nussknacker.engine.compile.nodecompilation can break pl.touk.nussknacker.engine.definition.component, while a change to pl.touk.nussknacker.engine.definition.component can't break pl.touk.nussknacker.engine.compile.nodecompilation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.definition.component uses a module listed above it, which is the healthy direction.
30→37 pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.definition.component uses a type in pl.touk.nussknacker.engine.
- The types involved
pl.touk.nussknacker.engine.definition.component.DynamicComponentStaticDefinitionDeterminer→pl.touk.nussknacker.engine.ScenarioCompilationDependencies
- Direction
- pl.touk.nussknacker.engine.definition.component uses pl.touk.nussknacker.engine, so a change to pl.touk.nussknacker.engine can break pl.touk.nussknacker.engine.definition.component, while a change to pl.touk.nussknacker.engine.definition.component can't break pl.touk.nussknacker.engine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→9 pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 12 pairs of types, where a type in pl.touk.nussknacker.ui.process uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.engine.api.process.ProcessIdWithNamepl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.ScenarioAttachmentService→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.ScenarioAttachmentService→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.ScenarioMetadata→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.ScenarioMetadata→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.ScenarioQuery→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.VersionsWithDifferencesService→pl.touk.nussknacker.engine.api.process.VersionId
- Direction
- pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.ui.process, while a change to pl.touk.nussknacker.ui.process can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process uses a module listed above it, which is the healthy direction.
31→15 pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.api✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.ui.process.NewProcessPreparer→pl.touk.nussknacker.engine.api.ProcessAdditionalFields
- Direction
- pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.ui.process, while a change to pl.touk.nussknacker.ui.process can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process uses a module listed above it, which is the healthy direction.
31→16 pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.api.graph✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.ui.process uses a type in pl.touk.nussknacker.engine.api.graph.
- The types involved
pl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.engine.api.graph.ScenarioGraphpl.touk.nussknacker.ui.process.ScenarioWithDetailsConversions→pl.touk.nussknacker.engine.api.graph.ScenarioGraphpl.touk.nussknacker.ui.process.VersionsWithDifferencesService→pl.touk.nussknacker.engine.api.graph.ScenarioGraph
- Direction
- pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.api.graph, so a change to pl.touk.nussknacker.engine.api.graph can break pl.touk.nussknacker.ui.process, while a change to pl.touk.nussknacker.ui.process can't break pl.touk.nussknacker.engine.api.graph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process uses a module listed above it, which is the healthy direction.
31→20 pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.ui.security.api✕
- Connections
- 10 pairs of types, where a type in pl.touk.nussknacker.ui.process uses a type in pl.touk.nussknacker.ui.security.api.
- The types involved
pl.touk.nussknacker.ui.process.ConfigScenarioToolbarService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.ProcessStateDefinitionService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.ScenarioAttachmentService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.ScenarioToolbarService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.ScenarioToolbarSettings→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.ToolbarButton→pl.touk.nussknacker.ui.security.api.RealLoggedUserpl.touk.nussknacker.ui.process.ToolbarHelper→pl.touk.nussknacker.ui.security.api.RealLoggedUserpl.touk.nussknacker.ui.process.ToolbarPanel→pl.touk.nussknacker.ui.security.api.RealLoggedUser
- Direction
- pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.ui.security.api, so a change to pl.touk.nussknacker.ui.security.api can break pl.touk.nussknacker.ui.process, while a change to pl.touk.nussknacker.ui.process can't break pl.touk.nussknacker.ui.security.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process uses a module listed above it, which is the healthy direction.
31→21 pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.canonicalgraph✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process uses a type in pl.touk.nussknacker.engine.canonicalgraph.
- The types involved
pl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcess
- Direction
- pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.canonicalgraph, so a change to pl.touk.nussknacker.engine.canonicalgraph can break pl.touk.nussknacker.ui.process, while a change to pl.touk.nussknacker.ui.process can't break pl.touk.nussknacker.engine.canonicalgraph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process uses a module listed above it, which is the healthy direction.
31→29 pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.ui.process.repository✕
- Connections
- 8 pairs of types, where a type in pl.touk.nussknacker.ui.process uses a type in pl.touk.nussknacker.ui.process.repository.
- The types involved
pl.touk.nussknacker.ui.process.ConfigScenarioToolbarService→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntitypl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntitypl.touk.nussknacker.ui.process.ScenarioToolbarService→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntitypl.touk.nussknacker.ui.process.ScenarioToolbarSettings→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntitypl.touk.nussknacker.ui.process.ScenarioWithDetailsConversions→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntitypl.touk.nussknacker.ui.process.ToolbarButton→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntitypl.touk.nussknacker.ui.process.ToolbarHelper→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntitypl.touk.nussknacker.ui.process.ToolbarPanel→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntity
- Direction
- pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.ui.process.repository, so a change to pl.touk.nussknacker.ui.process.repository can break pl.touk.nussknacker.ui.process, while a change to pl.touk.nussknacker.ui.process can't break pl.touk.nussknacker.ui.process.repository.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process uses a module listed above it, which is the healthy direction.
31→36 pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.api.deployment part of a loop✕
- Connections
- 11 pairs of types, where a type in pl.touk.nussknacker.ui.process uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.engine.api.deployment.DataFreshnessPolicypl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.engine.api.deployment.ProcessActionpl.touk.nussknacker.ui.process.DBProcessService→pl.touk.nussknacker.engine.api.deployment.ScenarioActionNamepl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.deployment.DeploymentResultpl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.deployment.ScenarioActionNamepl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.deployment.ScenarioActivityIdpl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.deployment.ScenarioAttachmentpl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.deployment.ScenarioCommentpl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.deployment.ScenarioIdpl.touk.nussknacker.ui.process.ScenarioActivityAuditLog→pl.touk.nussknacker.engine.api.deployment.ScenarioVersionId
- Direction
- pl.touk.nussknacker.ui.process uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.ui.process, while a change to pl.touk.nussknacker.ui.process can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→3 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.graph.expression.Expression.Language✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ScenarioTestExecutorService→pl.touk.nussknacker.engine.graph.expression.Expression.Language.Jsonpl.touk.nussknacker.ui.process.deployment.ScenarioTestExecutorServiceImpl→pl.touk.nussknacker.engine.graph.expression.Expression.Language.Json
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.graph.expression.Expression.Language, so a change to pl.touk.nussknacker.engine.graph.expression.Expression.Language can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.graph.expression.Expression.Language.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→6 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionInfoService→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→9 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionService→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.deployment.CommandContext→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.deployment.CommonCommandData→pl.touk.nussknacker.engine.api.process.ProcessIdWithNamepl.touk.nussknacker.ui.process.deployment.DeploymentManagerDispatcher→pl.touk.nussknacker.engine.api.process.ProcessIdWithNamepl.touk.nussknacker.ui.process.deployment.RunDeploymentResult→pl.touk.nussknacker.engine.api.process.VersionId
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→11 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionInfoService→pl.touk.nussknacker.engine.api.context.ProcessCompilationErrorpl.touk.nussknacker.ui.process.deployment.ScenarioResolver→pl.touk.nussknacker.engine.api.context.ProcessCompilationError
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→14 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionInfoService→pl.touk.nussknacker.engine.api.component.NodeComponentInfopl.touk.nussknacker.ui.process.deployment.ActionInfoService→pl.touk.nussknacker.engine.api.component.StaticParameterConfigpl.touk.nussknacker.ui.process.deployment.CommonDeploymentCommand→pl.touk.nussknacker.engine.api.component.NodesDeploymentDatapl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.engine.api.component.NodesDeploymentDatapl.touk.nussknacker.ui.process.deployment.RunDeploymentCommand→pl.touk.nussknacker.engine.api.component.NodesDeploymentDatapl.touk.nussknacker.ui.process.deployment.RunRedeploymentCommand→pl.touk.nussknacker.engine.api.component.NodesDeploymentData
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→15 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionInfoService→pl.touk.nussknacker.engine.api.ProcessVersionpl.touk.nussknacker.ui.process.deployment.CommonCommandData→pl.touk.nussknacker.engine.api.Commentpl.touk.nussknacker.ui.process.deployment.ScenarioTestExecutorService→pl.touk.nussknacker.engine.api.ProcessVersionpl.touk.nussknacker.ui.process.deployment.ScenarioTestExecutorServiceImpl→pl.touk.nussknacker.engine.api.ProcessVersion
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→16 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.graph✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.api.graph.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionInfoService→pl.touk.nussknacker.engine.api.graph.ScenarioGraph
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.graph, so a change to pl.touk.nussknacker.engine.api.graph can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.api.graph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→20 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.ui.security.api✕
- Connections
- 7 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.ui.security.api.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionInfoService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.deployment.CommonCommandData→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.deployment.DeploymentManagerDispatcher→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.deployment.ScenarioResolver→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.deployment.ScenarioTestExecutorService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.deployment.ScenarioTestExecutorServiceImpl→pl.touk.nussknacker.ui.security.api.LoggedUser
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.ui.security.api, so a change to pl.touk.nussknacker.ui.security.api can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.ui.security.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→21 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.canonicalgraph✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.canonicalgraph.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionInfoService→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.ui.process.deployment.ScenarioResolver→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.ui.process.deployment.ScenarioTestExecutorService→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.ui.process.deployment.ScenarioTestExecutorServiceImpl→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcess
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.canonicalgraph, so a change to pl.touk.nussknacker.engine.canonicalgraph can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.canonicalgraph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→22 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.deployment✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.deployment.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionService→pl.touk.nussknacker.engine.deployment.ScenarioGraphSourcepl.touk.nussknacker.ui.process.deployment.CommonDeploymentCommand→pl.touk.nussknacker.engine.deployment.ScenarioGraphSourcepl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.engine.deployment.ExternalDeploymentIdpl.touk.nussknacker.ui.process.deployment.RunDeploymentCommand→pl.touk.nussknacker.engine.deployment.ScenarioGraphSourcepl.touk.nussknacker.ui.process.deployment.RunDeploymentResult→pl.touk.nussknacker.engine.deployment.ExternalDeploymentIdpl.touk.nussknacker.ui.process.deployment.RunRedeploymentCommand→pl.touk.nussknacker.engine.deployment.ScenarioGraphSource
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.deployment, so a change to pl.touk.nussknacker.engine.deployment can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→29 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.ui.process.repository✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.ui.process.repository.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionService→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntitypl.touk.nussknacker.ui.process.deployment.CommandContext→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntitypl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntity
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.ui.process.repository, so a change to pl.touk.nussknacker.ui.process.repository can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.ui.process.repository.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.deployment uses a module listed above it, which is the healthy direction.
32→36 pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.deployment part of a loop✕
- Connections
- 10 pairs of types, where a type in pl.touk.nussknacker.ui.process.deployment uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.ui.process.deployment.ActionInfoService→pl.touk.nussknacker.engine.api.deployment.ScenarioActionNamepl.touk.nussknacker.ui.process.deployment.ActionService→pl.touk.nussknacker.engine.api.deployment.ProcessActionpl.touk.nussknacker.ui.process.deployment.ActionService→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.process.deployment.CommandContext→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.process.deployment.DeploymentManagerDispatcher→pl.touk.nussknacker.engine.api.deployment.DeploymentManagerpl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.engine.api.deployment.DMRunDeploymentCommandpl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.engine.api.deployment.DeploymentUpdateStrategypl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.engine.api.deployment.ProcessActionIdpl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.engine.api.deployment.RunOffScheduleResultpl.touk.nussknacker.ui.process.deployment.DeploymentService→pl.touk.nussknacker.engine.api.deployment.ScenarioActionName
- Direction
- pl.touk.nussknacker.ui.process.deployment uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.ui.process.deployment, while a change to pl.touk.nussknacker.ui.process.deployment can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→2 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.typed.typing✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.engine.api.typed.typing.
- The types involved
pl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.engine.api.typed.typing.TypingResult
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.typed.typing, so a change to pl.touk.nussknacker.engine.api.typed.typing can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.engine.api.typed.typing.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→9 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 20 pairs of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.ui.api.ActionInfoHttpService→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.api.AppApiHttpService→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.api.AuthorizeProcess→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.api.AuthorizeProcessDirectives→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.api.AuthorizeProcessDirectives→pl.touk.nussknacker.engine.api.process.ProcessIdWithNamepl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.api.ProcessDifference→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.api.ProcessDirectives→pl.touk.nussknacker.engine.api.process.ProcessIdWithNamepl.touk.nussknacker.ui.api.ProcessDirectives→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.api.ProcessReportResources→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.api.ProcessesExportResources→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.api.RemoteEnvironmentResources→pl.touk.nussknacker.engine.api.process.ProcessIdWithNamepl.touk.nussknacker.ui.api.RemoteEnvironmentResources→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.api.ScenarioActivityApiHttpService→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.api.ScenarioActivityApiHttpService→pl.touk.nussknacker.engine.api.process.ProcessIdWithNamepl.touk.nussknacker.ui.api.ScenarioActivityApiHttpService→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.api.ScenarioLiveDataApiHttpService→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.api.ScenarioLiveDataApiHttpService→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.api.ScenarioStatusPresenter→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.api.ScenarioValidationRequest→pl.touk.nussknacker.engine.api.process.ProcessName
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→11 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.ui.api.TestingApiErrorMessages→pl.touk.nussknacker.engine.api.context.ProcessCompilationError
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→15 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.ui.api.ProcessReportResources→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.ui.api.ProcessesExportResources→pl.touk.nussknacker.engine.api.ProcessVersionpl.touk.nussknacker.ui.api.ScenarioLiveDataApiHttpService→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.ui.api.ScenarioTestingApiHttpService→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.ui.api.TestingApiErrorMessages→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.ui.api.TestingApiErrorMessages→pl.touk.nussknacker.engine.api.NodeName
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→16 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.graph✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.engine.api.graph.
- The types involved
pl.touk.nussknacker.ui.api.ProcessReportResources→pl.touk.nussknacker.engine.api.graph.ScenarioGraphpl.touk.nussknacker.ui.api.ProcessesExportResources→pl.touk.nussknacker.engine.api.graph.ScenarioGraphpl.touk.nussknacker.ui.api.ScenarioValidationRequest→pl.touk.nussknacker.engine.api.graph.ScenarioGraph
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.graph, so a change to pl.touk.nussknacker.engine.api.graph can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.engine.api.graph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→20 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.ui.security.api✕
- Connections
- 18 pairs of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.ui.security.api.
- The types involved
pl.touk.nussknacker.ui.api.AppApiHttpService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.AuthorizeProcess→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.AuthorizeProcessDirectives→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.BaseHttpService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.DefinitionResources→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.ListenerApiUser→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.ProcessDirectives→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.ProcessReportResources→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.ProcessesExportResources→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.ProcessesResources→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.RemoteEnvironmentResources→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.RouteWithUser→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.ScenarioActivityApiHttpService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.ScenarioLiveDataApiHttpService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.ScenarioStatusPresenter→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.StatusResources→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.api.ValidationResources→pl.touk.nussknacker.ui.security.api.LoggedUser
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.ui.security.api, so a change to pl.touk.nussknacker.ui.security.api can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.ui.security.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→21 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.canonicalgraph✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.engine.canonicalgraph.
- The types involved
pl.touk.nussknacker.ui.api.ProcessesExportResources→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcess
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.canonicalgraph, so a change to pl.touk.nussknacker.engine.canonicalgraph can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.engine.canonicalgraph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→24 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.spel✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.engine.spel.
- The types involved
pl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.engine.spel.ExpressionSuggestion
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.spel, so a change to pl.touk.nussknacker.engine.spel can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.engine.spel.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→25 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos✕
- Connections
- 8 pairs of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.
- The types involved
pl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.ExpressionSuggestionRequestDtopl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationRequestpl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationRequestDtopl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodeValidationResultpl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.NodesErrorpl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.ParametersValidationRequestpl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.ParametersValidationRequestDtopl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.TestCaseAdditionalVariablesResponseDto
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos, so a change to pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.ui.api.description.NodesApiEndpoints.Dtos.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→29 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.ui.process.repository✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.ui.process.repository.
- The types involved
pl.touk.nussknacker.ui.api.ProcessesExportResources→pl.touk.nussknacker.ui.process.repository.ScenarioWithDetailsEntity
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.ui.process.repository, so a change to pl.touk.nussknacker.ui.process.repository can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.ui.process.repository.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→31 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.ui.process✕
- Connections
- 10 pairs of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.ui.process.
- The types involved
pl.touk.nussknacker.ui.api.ActionInfoHttpService→pl.touk.nussknacker.ui.process.ProcessServicepl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.ui.process.ProcessServicepl.touk.nussknacker.ui.api.ProcessDirectives→pl.touk.nussknacker.ui.process.ProcessServicepl.touk.nussknacker.ui.api.ProcessReportResources→pl.touk.nussknacker.ui.process.ProcessServicepl.touk.nussknacker.ui.api.ProcessesExportResources→pl.touk.nussknacker.ui.process.ProcessServicepl.touk.nussknacker.ui.api.ProcessesResources→pl.touk.nussknacker.ui.process.ProcessServicepl.touk.nussknacker.ui.api.ProcessesResources→pl.touk.nussknacker.ui.process.ScenarioQuerypl.touk.nussknacker.ui.api.RemoteEnvironmentResources→pl.touk.nussknacker.ui.process.ProcessServicepl.touk.nussknacker.ui.api.ScenarioLiveDataApiHttpService→pl.touk.nussknacker.ui.process.ProcessServicepl.touk.nussknacker.ui.api.ValidationResources→pl.touk.nussknacker.ui.process.ProcessService
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.ui.process, so a change to pl.touk.nussknacker.ui.process can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.ui.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.api uses a module listed above it, which is the healthy direction.
33→36 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.deployment part of a loop✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.ui.api.ScenarioActivityApiHttpService→pl.touk.nussknacker.engine.api.deployment.ScenarioActivityIdpl.touk.nussknacker.ui.api.ScenarioActivityApiHttpService→pl.touk.nussknacker.engine.api.deployment.ScenarioAttachmentpl.touk.nussknacker.ui.api.ScenarioActivityApiHttpService→pl.touk.nussknacker.engine.api.deployment.ScenarioCommentpl.touk.nussknacker.ui.api.ScenarioStatusPresenter→pl.touk.nussknacker.engine.api.deployment.StateStatus
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→37 pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.api uses a type in pl.touk.nussknacker.engine.
- The types involved
pl.touk.nussknacker.ui.api.NodesApiHttpService→pl.touk.nussknacker.engine.ModelData
- Direction
- pl.touk.nussknacker.ui.api uses pl.touk.nussknacker.engine, so a change to pl.touk.nussknacker.engine can break pl.touk.nussknacker.ui.api, while a change to pl.touk.nussknacker.ui.api can't break pl.touk.nussknacker.engine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→14 pl.touk.nussknacker.ui.config uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.ui.config uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.ui.config.AdditionalUIConfigProviderLoader→pl.touk.nussknacker.engine.api.component.AdditionalUIConfigProviderpl.touk.nussknacker.ui.config.ComponentLinkConfig→pl.touk.nussknacker.engine.api.component.ComponentTypepl.touk.nussknacker.ui.config.ComponentLinkConfig→pl.touk.nussknacker.engine.api.component.DesignerWideComponentId
- Direction
- pl.touk.nussknacker.ui.config uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.ui.config, while a change to pl.touk.nussknacker.ui.config can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.config uses a module listed above it, which is the healthy direction.
34→20 pl.touk.nussknacker.ui.config uses pl.touk.nussknacker.ui.security.api✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.config uses a type in pl.touk.nussknacker.ui.security.api.
- The types involved
pl.touk.nussknacker.ui.config.ComponentLinkConfig→pl.touk.nussknacker.ui.security.api.GlobalPermissionpl.touk.nussknacker.ui.config.ComponentLinkConfig→pl.touk.nussknacker.ui.security.api.LoggedUser
- Direction
- pl.touk.nussknacker.ui.config uses pl.touk.nussknacker.ui.security.api, so a change to pl.touk.nussknacker.ui.security.api can break pl.touk.nussknacker.ui.config, while a change to pl.touk.nussknacker.ui.config can't break pl.touk.nussknacker.ui.security.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.config uses a module listed above it, which is the healthy direction.
34→33 pl.touk.nussknacker.ui.config uses pl.touk.nussknacker.ui.api✕
- Connections
- 9 pairs of types, where a type in pl.touk.nussknacker.ui.config uses a type in pl.touk.nussknacker.ui.api.
- The types involved
pl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.ui.api.AssistantSettingspl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.ui.api.CommentSettingspl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.ui.api.DeploymentCommentSettingspl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.ui.api.EnvironmentAlertpl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.ui.api.IntervalTimeSettingspl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.ui.api.MetricsSettingspl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.ui.api.SurveySettingspl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.ui.api.TestDataSettingspl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.ui.api.TopTab
- Direction
- pl.touk.nussknacker.ui.config uses pl.touk.nussknacker.ui.api, so a change to pl.touk.nussknacker.ui.api can break pl.touk.nussknacker.ui.config, while a change to pl.touk.nussknacker.ui.config can't break pl.touk.nussknacker.ui.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.config uses a module listed above it, which is the healthy direction.
34→37 pl.touk.nussknacker.ui.config uses pl.touk.nussknacker.engine part of a loop✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.config uses a type in pl.touk.nussknacker.engine.
- The types involved
pl.touk.nussknacker.ui.config.DesignerConfig→pl.touk.nussknacker.engine.ConfigWithUnresolvedVersion
- Direction
- pl.touk.nussknacker.ui.config uses pl.touk.nussknacker.engine, so a change to pl.touk.nussknacker.engine can break pl.touk.nussknacker.ui.config, while a change to pl.touk.nussknacker.ui.config can't break pl.touk.nussknacker.engine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→9 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.process.ProcessName
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.processingtype uses a module listed above it, which is the healthy direction.
35→13 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.api.definition✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.definition.EngineScenarioCompilationDependencies
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.processingtype uses a module listed above it, which is the healthy direction.
35→14 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 7 pairs of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.DeploymentData→pl.touk.nussknacker.engine.api.component.ScenarioPropertyConfigpl.touk.nussknacker.ui.process.processingtype.DesignerModelData→pl.touk.nussknacker.engine.api.component.ProcessingModepl.touk.nussknacker.ui.process.processingtype.DesignerModelData→pl.touk.nussknacker.engine.api.component.ScenarioPropertyConfigpl.touk.nussknacker.ui.process.processingtype.ProcessingTypeServices→pl.touk.nussknacker.engine.api.component.ComponentAdditionalConfigpl.touk.nussknacker.ui.process.processingtype.ProcessingTypeServices→pl.touk.nussknacker.engine.api.component.DesignerWideComponentIdpl.touk.nussknacker.ui.process.processingtype.ScenarioParametersDeterminer→pl.touk.nussknacker.engine.api.component.ProcessingModepl.touk.nussknacker.ui.process.processingtype.ScenarioParametersService→pl.touk.nussknacker.engine.api.component.ProcessingMode
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.processingtype uses a module listed above it, which is the healthy direction.
35→20 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.ui.security.api✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.ui.security.api.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.ScenarioParametersService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.processingtype.ValueWithRestriction→pl.touk.nussknacker.ui.security.api.LoggedUser
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.ui.security.api, so a change to pl.touk.nussknacker.ui.security.api can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.ui.security.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.processingtype uses a module listed above it, which is the healthy direction.
35→22 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.deployment✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.engine.deployment.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.DeploymentData→pl.touk.nussknacker.engine.deployment.EngineSetupNamepl.touk.nussknacker.ui.process.processingtype.EngineNameInputData→pl.touk.nussknacker.engine.deployment.EngineSetupNamepl.touk.nussknacker.ui.process.processingtype.ScenarioParametersDeterminer→pl.touk.nussknacker.engine.deployment.EngineSetupNamepl.touk.nussknacker.ui.process.processingtype.ScenarioParametersService→pl.touk.nussknacker.engine.deployment.EngineSetupName
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.deployment, so a change to pl.touk.nussknacker.engine.deployment can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.engine.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.processingtype uses a module listed above it, which is the healthy direction.
35→30 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.definition.component✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.engine.definition.component.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.ScenarioParametersDeterminer→pl.touk.nussknacker.engine.definition.component.ComponentDefinitionWithImplementation
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.definition.component, so a change to pl.touk.nussknacker.engine.definition.component can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.engine.definition.component.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.processingtype uses a module listed above it, which is the healthy direction.
35→31 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.ui.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.ui.process.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.ProcessingTypeServices→pl.touk.nussknacker.ui.process.NewProcessPreparer
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.ui.process, so a change to pl.touk.nussknacker.ui.process can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.ui.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.processingtype uses a module listed above it, which is the healthy direction.
35→32 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.ui.process.deployment✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.ui.process.deployment.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.ProcessingTypeServices→pl.touk.nussknacker.ui.process.deployment.ActionInfoServicepl.touk.nussknacker.ui.process.processingtype.ProcessingTypeServices→pl.touk.nussknacker.ui.process.deployment.ScenarioResolver
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.ui.process.deployment, so a change to pl.touk.nussknacker.ui.process.deployment can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.ui.process.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.processingtype uses a module listed above it, which is the healthy direction.
35→34 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.ui.config✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.ui.config.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.ProcessingTypeConfigsLoaderLoader→pl.touk.nussknacker.ui.config.DesignerConfigpl.touk.nussknacker.ui.process.processingtype.ProcessingTypeConfigsLoaderLoader→pl.touk.nussknacker.ui.config.DesignerConfigLoader
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.ui.config, so a change to pl.touk.nussknacker.ui.config can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.ui.config.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.processingtype uses a module listed above it, which is the healthy direction.
35→36 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.api.deployment part of a loop✕
- Connections
- 11 pairs of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.DeploymentData→pl.touk.nussknacker.engine.api.deployment.DeploymentManagerpl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.DMScenarioCommandpl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.DataFreshnessPolicypl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.DeploymentManagerpl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.DeploymentStatusDetailspl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.DeploymentSynchronisationSupportpl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.DeploymentsStatusesQueryForAllScenariosSupportpl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.LiveDataPreviewSupportpl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.ProcessStateDefinitionManagerpl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.SchedulingSupportpl.touk.nussknacker.ui.process.processingtype.InvalidDeploymentManagerStub→pl.touk.nussknacker.engine.api.deployment.WithDataFreshnessStatus
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→37 pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine part of a loop✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.ui.process.processingtype uses a type in pl.touk.nussknacker.engine.
- The types involved
pl.touk.nussknacker.ui.process.processingtype.DeploymentData→pl.touk.nussknacker.engine.CustomProcessValidatorpl.touk.nussknacker.ui.process.processingtype.DeploymentData→pl.touk.nussknacker.engine.JobsRecoverySettingspl.touk.nussknacker.ui.process.processingtype.DeploymentData→pl.touk.nussknacker.engine.MetaDataInitializerpl.touk.nussknacker.ui.process.processingtype.DesignerModelData→pl.touk.nussknacker.engine.ModelData
- Direction
- pl.touk.nussknacker.ui.process.processingtype uses pl.touk.nussknacker.engine, so a change to pl.touk.nussknacker.engine can break pl.touk.nussknacker.ui.process.processingtype, while a change to pl.touk.nussknacker.ui.process.processingtype can't break pl.touk.nussknacker.engine.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→6 pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api.parameter✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.deployment uses a type in pl.touk.nussknacker.engine.api.parameter.
- The types involved
pl.touk.nussknacker.engine.api.deployment.WithActionParametersSupport→pl.touk.nussknacker.engine.api.parameter.ParameterName
- Direction
- pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api.parameter, so a change to pl.touk.nussknacker.engine.api.parameter can break pl.touk.nussknacker.engine.api.deployment, while a change to pl.touk.nussknacker.engine.api.deployment can't break pl.touk.nussknacker.engine.api.parameter.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.deployment uses a module listed above it, which is the healthy direction.
36→8 pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api.deployment uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation.
- The types involved
pl.touk.nussknacker.engine.api.deployment.DeploymentSynchronisationSupported→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.deployment.OverridingProcessStateDefinitionManager→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.deployment.ProcessActionState→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.engine.api.deployment.ProcessStateDefinitionManager→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.engine.api.deployment, while a change to pl.touk.nussknacker.engine.api.deployment can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.deployment uses a module listed above it, which is the healthy direction.
36→9 pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 10 pairs of types, where a type in pl.touk.nussknacker.engine.api.deployment uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.api.deployment.DMCancelDeploymentCommand→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.deployment.DMCancelScenarioCommand→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.deployment.DMMakeScenarioSavepointCommand→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.deployment.DMStopDeploymentCommand→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.deployment.DMStopScenarioCommand→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.deployment.DeploymentManager→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.deployment.DeploymentsStatusesQueryForAllScenariosSupported→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.api.deployment.ProcessAction→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.engine.api.deployment.ProcessAction→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.engine.api.deployment.ScenarioStatusActionDetails→pl.touk.nussknacker.engine.api.process.VersionId
- Direction
- pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine.api.deployment, while a change to pl.touk.nussknacker.engine.api.deployment can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.deployment uses a module listed above it, which is the healthy direction.
36→13 pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api.definition✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.deployment uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.api.deployment.DeploymentManager→pl.touk.nussknacker.engine.api.definition.EngineScenarioCompilationDependencies
- Direction
- pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine.api.deployment, while a change to pl.touk.nussknacker.engine.api.deployment can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.deployment uses a module listed above it, which is the healthy direction.
36→14 pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine.api.deployment uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.api.deployment.WithActionParametersSupport→pl.touk.nussknacker.engine.api.component.StaticParameterConfig
- Direction
- pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine.api.deployment, while a change to pl.touk.nussknacker.engine.api.deployment can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.deployment uses a module listed above it, which is the healthy direction.
36→15 pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api.deployment uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.api.deployment.DMRunDeploymentCommand→pl.touk.nussknacker.engine.api.ProcessVersionpl.touk.nussknacker.engine.api.deployment.DMRunOffScheduleCommand→pl.touk.nussknacker.engine.api.ProcessVersionpl.touk.nussknacker.engine.api.deployment.DMTestScenarioCommand→pl.touk.nussknacker.engine.api.ProcessVersionpl.touk.nussknacker.engine.api.deployment.DMValidateScenarioCommand→pl.touk.nussknacker.engine.api.ProcessVersion
- Direction
- pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine.api.deployment, while a change to pl.touk.nussknacker.engine.api.deployment can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.deployment uses a module listed above it, which is the healthy direction.
36→21 pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.canonicalgraph✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api.deployment uses a type in pl.touk.nussknacker.engine.canonicalgraph.
- The types involved
pl.touk.nussknacker.engine.api.deployment.DMRunDeploymentCommand→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.engine.api.deployment.DMRunOffScheduleCommand→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.engine.api.deployment.DMTestScenarioCommand→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcesspl.touk.nussknacker.engine.api.deployment.DMValidateScenarioCommand→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcess
- Direction
- pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.canonicalgraph, so a change to pl.touk.nussknacker.engine.canonicalgraph can break pl.touk.nussknacker.engine.api.deployment, while a change to pl.touk.nussknacker.engine.api.deployment can't break pl.touk.nussknacker.engine.canonicalgraph.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.deployment uses a module listed above it, which is the healthy direction.
36→22 pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.deployment✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine.api.deployment uses a type in pl.touk.nussknacker.engine.deployment.
- The types involved
pl.touk.nussknacker.engine.api.deployment.DMCancelDeploymentCommand→pl.touk.nussknacker.engine.deployment.DeploymentIdpl.touk.nussknacker.engine.api.deployment.DMStopDeploymentCommand→pl.touk.nussknacker.engine.deployment.DeploymentIdpl.touk.nussknacker.engine.api.deployment.DeploymentStatusDetails→pl.touk.nussknacker.engine.deployment.DeploymentIdpl.touk.nussknacker.engine.api.deployment.DeploymentSynchronisationSupported→pl.touk.nussknacker.engine.deployment.DeploymentId
- Direction
- pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.engine.deployment, so a change to pl.touk.nussknacker.engine.deployment can break pl.touk.nussknacker.engine.api.deployment, while a change to pl.touk.nussknacker.engine.api.deployment can't break pl.touk.nussknacker.engine.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.deployment uses a module listed above it, which is the healthy direction.
36→35 pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.ui.process.processingtype✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine.api.deployment uses a type in pl.touk.nussknacker.ui.process.processingtype.
- The types involved
pl.touk.nussknacker.engine.api.deployment.DMRunDeploymentCommand→pl.touk.nussknacker.ui.process.processingtype.DeploymentDatapl.touk.nussknacker.engine.api.deployment.DMValidateScenarioCommand→pl.touk.nussknacker.ui.process.processingtype.DeploymentData
- Direction
- pl.touk.nussknacker.engine.api.deployment uses pl.touk.nussknacker.ui.process.processingtype, so a change to pl.touk.nussknacker.ui.process.processingtype can break pl.touk.nussknacker.engine.api.deployment, while a change to pl.touk.nussknacker.engine.api.deployment can't break pl.touk.nussknacker.ui.process.processingtype.
- Position
- Below the diagonal: pl.touk.nussknacker.engine.api.deployment uses a module listed above it, which is the healthy direction.
37→7 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.graph.node✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.graph.node.
- The types involved
pl.touk.nussknacker.engine.Interpreter→pl.touk.nussknacker.engine.graph.node.Nodepl.touk.nussknacker.engine.InterpreterInternal→pl.touk.nussknacker.engine.graph.node.Node
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.graph.node, so a change to pl.touk.nussknacker.engine.graph.node can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.graph.node.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
37→9 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 4 pairs of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.engine.ClassLoaderModelData→pl.touk.nussknacker.engine.api.process.ProcessConfigCreatorpl.touk.nussknacker.engine.Interpreter→pl.touk.nussknacker.engine.api.process.ServiceExecutionContextpl.touk.nussknacker.engine.MetaDataInitializer→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.engine.RuntimeMode→pl.touk.nussknacker.engine.api.process.ComponentUseContext
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
37→11 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.context✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.api.context.
- The types involved
pl.touk.nussknacker.engine.CustomProcessValidator→pl.touk.nussknacker.engine.api.context.ProcessCompilationError
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.context, so a change to pl.touk.nussknacker.engine.api.context can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.api.context.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
37→13 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.definition✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.api.definition.
- The types involved
pl.touk.nussknacker.engine.ScenarioCompilationDependencies→pl.touk.nussknacker.engine.api.definition.EngineScenarioCompilationDependencies
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.definition, so a change to pl.touk.nussknacker.engine.api.definition can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.api.definition.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
37→14 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 7 pairs of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.engine.ClassLoaderModelData→pl.touk.nussknacker.engine.api.component.ComponentAdditionalConfigpl.touk.nussknacker.engine.ClassLoaderModelData→pl.touk.nussknacker.engine.api.component.ComponentIdpl.touk.nussknacker.engine.ClassLoaderModelData→pl.touk.nussknacker.engine.api.component.DesignerWideComponentIdpl.touk.nussknacker.engine.DeploymentManagerProvider→pl.touk.nussknacker.engine.api.component.ScenarioPropertyConfigpl.touk.nussknacker.engine.ModelDependencies→pl.touk.nussknacker.engine.api.component.ComponentAdditionalConfigpl.touk.nussknacker.engine.ModelDependencies→pl.touk.nussknacker.engine.api.component.ComponentIdpl.touk.nussknacker.engine.ModelDependencies→pl.touk.nussknacker.engine.api.component.DesignerWideComponentId
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
37→15 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api✕
- Connections
- 12 pairs of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.api.
- The types involved
pl.touk.nussknacker.engine.DeploymentManagerProvider→pl.touk.nussknacker.engine.api.NamedServiceProviderpl.touk.nussknacker.engine.InterpretationResult→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.InterpretationResult→pl.touk.nussknacker.engine.api.PartReferencepl.touk.nussknacker.engine.Interpreter→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.Interpreter→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.InterpreterInternal→pl.touk.nussknacker.engine.api.Contextpl.touk.nussknacker.engine.InterpreterInternal→pl.touk.nussknacker.engine.api.NodeIdpl.touk.nussknacker.engine.InterpreterInternal→pl.touk.nussknacker.engine.api.PartReferencepl.touk.nussknacker.engine.InterpreterInternal→pl.touk.nussknacker.engine.api.ValueWithContextpl.touk.nussknacker.engine.MetaDataInitializer→pl.touk.nussknacker.engine.api.MetaDatapl.touk.nussknacker.engine.ScenarioCompilationDependencies→pl.touk.nussknacker.engine.api.JobDatapl.touk.nussknacker.engine.ScenarioCompilationDependencies→pl.touk.nussknacker.engine.api.MetaData
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api, so a change to pl.touk.nussknacker.engine.api can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.api.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
37→17 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.expression.parse✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.expression.parse.
- The types involved
pl.touk.nussknacker.engine.InterpreterInternal→pl.touk.nussknacker.engine.expression.parse.CompiledExpression
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.expression.parse, so a change to pl.touk.nussknacker.engine.expression.parse can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.expression.parse.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
37→21 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.canonicalgraph✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.canonicalgraph.
- The types involved
pl.touk.nussknacker.engine.CustomProcessValidator→pl.touk.nussknacker.engine.canonicalgraph.CanonicalProcess
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.canonicalgraph, so a change to pl.touk.nussknacker.engine.canonicalgraph can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.canonicalgraph.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
37→22 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.deployment✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.deployment.
- The types involved
pl.touk.nussknacker.engine.DeploymentManagerProvider→pl.touk.nussknacker.engine.deployment.EngineSetupNamepl.touk.nussknacker.engine.ModelConfigs→pl.touk.nussknacker.engine.deployment.AdditionalModelConfigspl.touk.nussknacker.engine.ProcessingTypeConfig→pl.touk.nussknacker.engine.deployment.EngineSetupName
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.deployment, so a change to pl.touk.nussknacker.engine.deployment can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
37→36 pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.deployment✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.engine uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.engine.DeploymentManagerProvider→pl.touk.nussknacker.engine.api.deployment.DeploymentManager
- Direction
- pl.touk.nussknacker.engine uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.engine, while a change to pl.touk.nussknacker.engine can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.engine uses a module listed above it, which is the healthy direction.
38→4 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.graph.expression.TabularTypedData✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.engine.graph.expression.TabularTypedData.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.engine.graph.expression.TabularTypedData.Error
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.graph.expression.TabularTypedData, so a change to pl.touk.nussknacker.engine.graph.expression.TabularTypedData can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.engine.graph.expression.TabularTypedData.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
38→8 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.graph.node.VariableOperation✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.engine.graph.node.VariableOperation.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.DeploymentRepository→pl.touk.nussknacker.engine.graph.node.VariableOperation.Setpl.touk.nussknacker.ui.process.newdeployment.ScenarioStatusProvider→pl.touk.nussknacker.engine.graph.node.VariableOperation.Set
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.graph.node.VariableOperation, so a change to pl.touk.nussknacker.engine.graph.node.VariableOperation can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.engine.graph.node.VariableOperation.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
38→9 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 8 pairs of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.Deployment→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.newdeployment.DeploymentEntityFactory→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.newdeployment.DeploymentEntityFactory→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.newdeployment.DeploymentRepository→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.engine.api.process.VersionIdpl.touk.nussknacker.ui.process.newdeployment.RunDeploymentCommand→pl.touk.nussknacker.engine.api.process.ProcessNamepl.touk.nussknacker.ui.process.newdeployment.ScenarioStatusProvider→pl.touk.nussknacker.engine.api.process.ProcessName
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
38→14 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.engine.api.component.NodesDeploymentDatapl.touk.nussknacker.ui.process.newdeployment.RunDeploymentCommand→pl.touk.nussknacker.engine.api.component.NodesDeploymentData
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
38→20 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.ui.security.api✕
- Connections
- 3 pairs of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.ui.security.api.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.newdeployment.RunDeploymentCommand→pl.touk.nussknacker.ui.security.api.LoggedUserpl.touk.nussknacker.ui.process.newdeployment.ScenarioStatusProvider→pl.touk.nussknacker.ui.security.api.LoggedUser
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.ui.security.api, so a change to pl.touk.nussknacker.ui.security.api can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.ui.security.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
38→22 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.deployment✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.engine.deployment.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.Deployment→pl.touk.nussknacker.engine.deployment.DeploymentIdpl.touk.nussknacker.ui.process.newdeployment.DeploymentCommand→pl.touk.nussknacker.engine.deployment.DeploymentIdpl.touk.nussknacker.ui.process.newdeployment.DeploymentEntityFactory→pl.touk.nussknacker.engine.deployment.DeploymentIdpl.touk.nussknacker.ui.process.newdeployment.DeploymentRepository→pl.touk.nussknacker.engine.deployment.DeploymentIdpl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.engine.deployment.DeploymentIdpl.touk.nussknacker.ui.process.newdeployment.RunDeploymentCommand→pl.touk.nussknacker.engine.deployment.DeploymentId
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.deployment, so a change to pl.touk.nussknacker.engine.deployment can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.engine.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
38→27 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.ui.db.entity✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.ui.db.entity.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.DeploymentEntityFactory→pl.touk.nussknacker.ui.db.entity.BaseEntityFactory
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.ui.db.entity, so a change to pl.touk.nussknacker.ui.db.entity can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.ui.db.entity.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
38→31 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.ui.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.ui.process.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.ui.process.ScenarioMetadata
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.ui.process, so a change to pl.touk.nussknacker.ui.process can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.ui.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
38→32 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.ui.process.deployment✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.ui.process.deployment.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.ui.process.deployment.RunDeploymentCommand
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.ui.process.deployment, so a change to pl.touk.nussknacker.ui.process.deployment can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.ui.process.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
38→36 pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.api.deployment✕
- Connections
- 6 pairs of types, where a type in pl.touk.nussknacker.ui.process.newdeployment uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.ui.process.newdeployment.Deployment→pl.touk.nussknacker.engine.api.deployment.DeploymentStatuspl.touk.nussknacker.ui.process.newdeployment.DeploymentEntityFactory→pl.touk.nussknacker.engine.api.deployment.DeploymentStatusNamepl.touk.nussknacker.ui.process.newdeployment.DeploymentRepository→pl.touk.nussknacker.engine.api.deployment.DeploymentStatuspl.touk.nussknacker.ui.process.newdeployment.DeploymentRepository→pl.touk.nussknacker.engine.api.deployment.DeploymentStatusNamepl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.engine.api.deployment.DeploymentStatuspl.touk.nussknacker.ui.process.newdeployment.DeploymentService→pl.touk.nussknacker.engine.api.deployment.DeploymentUpdateStrategy
- Direction
- pl.touk.nussknacker.ui.process.newdeployment uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.ui.process.newdeployment, while a change to pl.touk.nussknacker.ui.process.newdeployment can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.process.newdeployment uses a module listed above it, which is the healthy direction.
39→9 pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.api.process✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.statistics uses a type in pl.touk.nussknacker.engine.api.process.
- The types involved
pl.touk.nussknacker.ui.statistics.ScenarioStatisticsInputData→pl.touk.nussknacker.engine.api.process.ProcessIdpl.touk.nussknacker.ui.statistics.ScenarioStatisticsInputData→pl.touk.nussknacker.engine.api.process.VersionId
- Direction
- pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.api.process, so a change to pl.touk.nussknacker.engine.api.process can break pl.touk.nussknacker.ui.statistics, while a change to pl.touk.nussknacker.ui.statistics can't break pl.touk.nussknacker.engine.api.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.statistics uses a module listed above it, which is the healthy direction.
39→14 pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.api.component✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.statistics uses a type in pl.touk.nussknacker.engine.api.component.
- The types involved
pl.touk.nussknacker.ui.statistics.ScenarioStatistics→pl.touk.nussknacker.engine.api.component.DesignerWideComponentIdpl.touk.nussknacker.ui.statistics.ScenarioStatisticsInputData→pl.touk.nussknacker.engine.api.component.ProcessingMode
- Direction
- pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.api.component, so a change to pl.touk.nussknacker.engine.api.component can break pl.touk.nussknacker.ui.statistics, while a change to pl.touk.nussknacker.ui.statistics can't break pl.touk.nussknacker.engine.api.component.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.statistics uses a module listed above it, which is the healthy direction.
39→16 pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.api.graph✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.statistics uses a type in pl.touk.nussknacker.engine.api.graph.
- The types involved
pl.touk.nussknacker.ui.statistics.UsageStatisticsReportsSettingsService→pl.touk.nussknacker.engine.api.graph.ScenarioGraph
- Direction
- pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.api.graph, so a change to pl.touk.nussknacker.engine.api.graph can break pl.touk.nussknacker.ui.statistics, while a change to pl.touk.nussknacker.ui.statistics can't break pl.touk.nussknacker.engine.api.graph.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.statistics uses a module listed above it, which is the healthy direction.
39→29 pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.ui.process.repository✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.statistics uses a type in pl.touk.nussknacker.ui.process.repository.
- The types involved
pl.touk.nussknacker.ui.statistics.FingerprintService→pl.touk.nussknacker.ui.process.repository.DBIOActionRunnerpl.touk.nussknacker.ui.statistics.UsageStatisticsReportsSettingsService→pl.touk.nussknacker.ui.process.repository.DBIOActionRunner
- Direction
- pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.ui.process.repository, so a change to pl.touk.nussknacker.ui.process.repository can break pl.touk.nussknacker.ui.statistics, while a change to pl.touk.nussknacker.ui.statistics can't break pl.touk.nussknacker.ui.process.repository.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.statistics uses a module listed above it, which is the healthy direction.
39→30 pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.definition.component✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.statistics uses a type in pl.touk.nussknacker.engine.definition.component.
- The types involved
pl.touk.nussknacker.ui.statistics.ScenarioStatistics→pl.touk.nussknacker.engine.definition.component.ComponentDefinitionWithImplementationpl.touk.nussknacker.ui.statistics.UsageStatisticsReportsSettingsService→pl.touk.nussknacker.engine.definition.component.ComponentDefinitionWithImplementation
- Direction
- pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.definition.component, so a change to pl.touk.nussknacker.engine.definition.component can break pl.touk.nussknacker.ui.statistics, while a change to pl.touk.nussknacker.ui.statistics can't break pl.touk.nussknacker.engine.definition.component.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.statistics uses a module listed above it, which is the healthy direction.
39→31 pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.ui.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.statistics uses a type in pl.touk.nussknacker.ui.process.
- The types involved
pl.touk.nussknacker.ui.statistics.UsageStatisticsReportsSettingsService→pl.touk.nussknacker.ui.process.ProcessService
- Direction
- pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.ui.process, so a change to pl.touk.nussknacker.ui.process can break pl.touk.nussknacker.ui.statistics, while a change to pl.touk.nussknacker.ui.statistics can't break pl.touk.nussknacker.ui.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.statistics uses a module listed above it, which is the healthy direction.
39→34 pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.ui.config✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.statistics uses a type in pl.touk.nussknacker.ui.config.
- The types involved
pl.touk.nussknacker.ui.statistics.FingerprintService→pl.touk.nussknacker.ui.config.UsageStatisticsReportsConfigpl.touk.nussknacker.ui.statistics.UsageStatisticsReportsSettingsService→pl.touk.nussknacker.ui.config.UsageStatisticsReportsConfig
- Direction
- pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.ui.config, so a change to pl.touk.nussknacker.ui.config can break pl.touk.nussknacker.ui.statistics, while a change to pl.touk.nussknacker.ui.statistics can't break pl.touk.nussknacker.ui.config.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.statistics uses a module listed above it, which is the healthy direction.
39→36 pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.api.deployment✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.statistics uses a type in pl.touk.nussknacker.engine.api.deployment.
- The types involved
pl.touk.nussknacker.ui.statistics.ScenarioStatisticsInputData→pl.touk.nussknacker.engine.api.deployment.ProcessAction
- Direction
- pl.touk.nussknacker.ui.statistics uses pl.touk.nussknacker.engine.api.deployment, so a change to pl.touk.nussknacker.engine.api.deployment can break pl.touk.nussknacker.ui.statistics, while a change to pl.touk.nussknacker.ui.statistics can't break pl.touk.nussknacker.engine.api.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.statistics uses a module listed above it, which is the healthy direction.
40→19 pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.engine.util✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.factory uses a type in pl.touk.nussknacker.engine.util.
- The types involved
pl.touk.nussknacker.ui.factory.InfrastructureServices→pl.touk.nussknacker.engine.util.ExecutionContextWithIORuntime
- Direction
- pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.engine.util, so a change to pl.touk.nussknacker.engine.util can break pl.touk.nussknacker.ui.factory, while a change to pl.touk.nussknacker.ui.factory can't break pl.touk.nussknacker.engine.util.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.factory uses a module listed above it, which is the healthy direction.
40→29 pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process.repository✕
- Connections
- 5 pairs of types, where a type in pl.touk.nussknacker.ui.factory uses a type in pl.touk.nussknacker.ui.process.repository.
- The types involved
pl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.process.repository.FetchingProcessRepositorypl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.process.repository.ScenarioActionRepositorypl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.process.repository.ScenarioLabelsRepositorypl.touk.nussknacker.ui.factory.InfrastructureServices→pl.touk.nussknacker.ui.process.repository.DBIOActionRunnerpl.touk.nussknacker.ui.factory.NussknackerAppFactory→pl.touk.nussknacker.ui.process.repository.FetchingProcessRepository
- Direction
- pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process.repository, so a change to pl.touk.nussknacker.ui.process.repository can break pl.touk.nussknacker.ui.factory, while a change to pl.touk.nussknacker.ui.factory can't break pl.touk.nussknacker.ui.process.repository.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.factory uses a module listed above it, which is the healthy direction.
40→31 pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.factory uses a type in pl.touk.nussknacker.ui.process.
- The types involved
pl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.process.ProcessService
- Direction
- pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process, so a change to pl.touk.nussknacker.ui.process can break pl.touk.nussknacker.ui.factory, while a change to pl.touk.nussknacker.ui.factory can't break pl.touk.nussknacker.ui.process.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.factory uses a module listed above it, which is the healthy direction.
40→32 pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process.deployment✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.factory uses a type in pl.touk.nussknacker.ui.process.deployment.
- The types involved
pl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.process.deployment.ActionServicepl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.process.deployment.DeploymentManagerDispatcher
- Direction
- pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process.deployment, so a change to pl.touk.nussknacker.ui.process.deployment can break pl.touk.nussknacker.ui.factory, while a change to pl.touk.nussknacker.ui.factory can't break pl.touk.nussknacker.ui.process.deployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.factory uses a module listed above it, which is the healthy direction.
40→33 pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.api✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.factory uses a type in pl.touk.nussknacker.ui.api.
- The types involved
pl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.api.AuthorizeProcesspl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.api.ScenarioStatusPresenter
- Direction
- pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.api, so a change to pl.touk.nussknacker.ui.api can break pl.touk.nussknacker.ui.factory, while a change to pl.touk.nussknacker.ui.factory can't break pl.touk.nussknacker.ui.api.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.factory uses a module listed above it, which is the healthy direction.
40→34 pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.config✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.factory uses a type in pl.touk.nussknacker.ui.config.
- The types involved
pl.touk.nussknacker.ui.factory.NussknackerAppFactory→pl.touk.nussknacker.ui.config.DesignerConfig
- Direction
- pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.config, so a change to pl.touk.nussknacker.ui.config can break pl.touk.nussknacker.ui.factory, while a change to pl.touk.nussknacker.ui.factory can't break pl.touk.nussknacker.ui.config.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.factory uses a module listed above it, which is the healthy direction.
40→35 pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process.processingtype✕
- Connections
- 2 pairs of types, where a type in pl.touk.nussknacker.ui.factory uses a type in pl.touk.nussknacker.ui.process.processingtype.
- The types involved
pl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.process.processingtype.CombinedProcessingTypeDatapl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.process.processingtype.ProcessingTypeServices
- Direction
- pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process.processingtype, so a change to pl.touk.nussknacker.ui.process.processingtype can break pl.touk.nussknacker.ui.factory, while a change to pl.touk.nussknacker.ui.factory can't break pl.touk.nussknacker.ui.process.processingtype.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.factory uses a module listed above it, which is the healthy direction.
40→38 pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process.newdeployment✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.factory uses a type in pl.touk.nussknacker.ui.process.newdeployment.
- The types involved
pl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.process.newdeployment.DeploymentRepository
- Direction
- pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.process.newdeployment, so a change to pl.touk.nussknacker.ui.process.newdeployment can break pl.touk.nussknacker.ui.factory, while a change to pl.touk.nussknacker.ui.factory can't break pl.touk.nussknacker.ui.process.newdeployment.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.factory uses a module listed above it, which is the healthy direction.
40→39 pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.statistics✕
- Connections
- 1 pair of types, where a type in pl.touk.nussknacker.ui.factory uses a type in pl.touk.nussknacker.ui.statistics.
- The types involved
pl.touk.nussknacker.ui.factory.DomainServices→pl.touk.nussknacker.ui.statistics.FingerprintService
- Direction
- pl.touk.nussknacker.ui.factory uses pl.touk.nussknacker.ui.statistics, so a change to pl.touk.nussknacker.ui.statistics can break pl.touk.nussknacker.ui.factory, while a change to pl.touk.nussknacker.ui.factory can't break pl.touk.nussknacker.ui.statistics.
- Position
- Below the diagonal: pl.touk.nussknacker.ui.factory uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 158 | High / Critical |
| A05:2025 — Injection | 93 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A01:2025 — Broken Access Control | 1 | Medium |
Roadmap
First, establish a solid page structure by defining the language, title, and main landmark while ensuring proper heading order and disabling meta-refresh. Next, address the extensive form and button labeling gaps to ensure every control is programmatically accessible, and fix keyboard navigation for custom controls by adding proper roles and handlers. Finally, resolve the leaked secret in the configuration file and update all media elements with appropriate text alternatives to complete the accessibility and security remediation.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +3.7 pts | Low | REDACTED Scanning |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +5.0 pts | Medium | Page structure |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +4.0 pts | Medium | Forms & labels |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.9 pts | Medium | Keyboard semantics |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +2.9 pts | Medium | Text alternatives |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +2.9 pts | Medium | Dependency Hygiene |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with cypress-axe in tests, then gate axe/pa11y/Lighthouse in CI. | +2.6 pts | Medium | A11y enforcement |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.2 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High vulnerability: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala | 3.1 | Slop | Change Coupling: Boundary-crossing change coupling: Interpreter.scala ↔ LoggingListener.scala |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala | 5.6 | Mixed | Cyclomatic Complexity: DbScenarioActivityRepository.fromEntity (cyclomatic 43) |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): High secret: REDACTED |
| scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| designer/client/src/reducers/graph/reducer.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala | 6.0 | Mixed | Explicit Debt: TodoComment |
| designer/client/src/components/graph/SelectionContextProvider.tsx | 6.0 | Mixed | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 92 of 92 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 92 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2050 of 2154 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .scala, and our analyzer cannot run the .scala test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 41.9% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. In the meantime, produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`, or `addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures and real coverage will be read. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then both halves are read on the next scan.
- D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 635 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 725 test source file(s) (.scala, .java) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .scala, and the scala executor ran against the .scala half and could not be re-run to completion inside our analyzer environment — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in designer/client/ (695 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The remedy is our analyzer environment, not a runner nobody has built.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala`, `designer/client/src/components/MenuBar/useStateWithRevertTimeout.tsx`, `designer/client/src/components/graph/node-modal/BaseBuilderFieldWrapper.tsx`, `designer/client/src/components/graph/node-modal/fragment-input-definition/TypeSelect.tsx`, `designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala`, … (+2 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AC6 Visual & motion safety — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Spring (Scala), whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX2 Stateful singletons — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Those languages run requests on shared-memory threads, so a shared instance mutated without a lock is the same defect this card counts in C#, Java, Kotlin, Python, Go, Swift, Scala, Ruby and F#, but their singleton shapes are not read yet. That is a gap in this analyzer's language reach — not a finding that the code is free of it.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (examples/installation/docker-compose.yml). compose up failed (exit 18 — an image could not be pulled) — kafka Error Get "https://registry-1.docker.io/v2/": Forbidden grafana Error context canceled telegraf Error context canceled postgres Error context canceled nginx Error context canceled influxdb Error context canceled akhq Error context canceled designer Error context canceled schema-registry Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: grafana Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error context canceled kafka Error context canceled akhq Error context canceled schema-registry Error context canceled telegraf Error context canceled influxdb Error context canceled designer Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 85 further occurrence(s) are not listed individually; the score already reflects all 125.
- R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 437 further occurrence(s) are not listed individually; the score already reflects all 477.
- R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 202 further occurrence(s) are not listed individually; the score already reflects all 242.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
60 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SpelTyper.typeNode at 143. A further 35 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being PrettyValidationErrors.formatErrorMessage at 69 — they are counted neither in the figure above nor in this dimension's score. 29 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/encode/ToAvroSchemaBasedEncoder.scala (ToAvroSchemaBasedEncoder.encode at 48), designer/client/src/containers/event-tracking/helpers.ts (helpers.mapToolbarButtonToStatisticsEvent at 42), components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/encoders/ToJsonEncoderWithFallback.scala (ToJsonEncoderWithFallback.encodeValue at 41), designer/client/src/windowManager/ContentGetter.tsx (ContentGetter.contentGetter at 29), utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/AvroDefaultExpressionDeterminer.scala (AvroDefaultExpressionDeterminer.determine at 25), and 24 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with SpelTyper.typeNode (cyclomatic 143), CompareVersionsDialog.VersionsForm (cyclomatic 62). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
91 method(s) exceeded the cognitive complexity threshold of 15; the worst was SpelTyper.typeNode at 146.
What to do
- Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with SpelTyper.typeNode (cognitive 146), SpelExpressionSuggester.expressionSuggestionsAux (cognitive 107), drawText.buildFragmentsForTokens::wrapAndPushWords (cognitive 75). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
54 god class(es) detected.
What to do
- Resolve the 35 FunctionTooLong finding(s) in God Classes — start with useDataMapper.ts, FieldRow.tsx, DataMapper.tsx. — One of this dimension's main actionable groups (35 warning-level).
- Resolve the 9 FileTooLong finding(s) in God Classes — start with NodesApiEndpoints.scala, HttpService.ts, DbScenarioActivityRepository.scala. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 6 TooManyMethods finding(s) in God Classes — start with HttpService.ts, Graph.tsx, DbScenarioActivityRepository.scala. — One of this dimension's main actionable groups (6 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
31 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 1 of the 32 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .tsx (25% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with InvalidateComponentsUsagesCache.scala, ExpressionsMigration.scala, collection.scala. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with PeriodicProcessService.scala, CaseClassTypeInfo.scala, UniversalKafkaSourceFactory.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with NodeDependency.scala, UnionTransformer.scala. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
79 production modules (npm+sbt), 0 dependency cycle(s), 4 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 2 module(s) off the main sequence, with abstractness counted on 19 of the 79 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Unstable project flinkDeploymentManager finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project flinkExecutor finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project flinkKafkaComponentsUtils finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
8 of 209 classes have LCOM4 above 3.
What to do
- Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with CaseClassTypeComparator.scala, DbScenarioActivityRepository.scala, TableSource.scala. — One of this dimension's main actionable groups (8 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
4257 test methods: 4015 unit, 108 integration, 0 BDD, 134 e2e. The JavaScript/TypeScript suite contributes 635 `it`/`test` case(s) across 94 test file(s) declaring at least one; its tier split is read from package names and paths only. The Scala suite contributes 3622 test case(s) across 519 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D10 · Test Quality
0 skipped, 25 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 635 tests. Measured on the JavaScript/TypeScript suite only — at least 725 test source file(s) (.scala, .java) went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 25 No assertions finding(s) in Test Quality — start with autoScreenshotChangeDocs.cy.ts (12), typeHelpers.test.ts (5), processSelection.cy.ts (4). — One of this dimension's main actionable groups (25 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
75 outdated direct sbt declarations. 81 of 84 direct declarations were graded against Maven Central (3 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 81 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 7 sbt build file(s) (REDACTED and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 68 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 3 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
Top hotspots: designer/client/src/components/modals/CompareVersionsDialog.tsx (2×62=124)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with CompareVersionsDialog.tsx. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
47 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is designer/client/src/components/conditionBuilder/ConditionBuilder.tsx. Counted over 1017 of the 2649 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
705 deducted task-comment markers across 182261 LoC (0.4/KLoC) → score 9.2. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 616 TodoComment finding(s) in Explicit Debt — start with node.scala (13), typing.scala (10), SpelTyper.scala (8). — One of this dimension's main actionable groups (616 warning-level).
- Resolve the 73 FixmeComment finding(s) in Explicit Debt — start with LiteKafkaUniversalAvroSchemaFunctionalTest.scala (7), RequestResponseTestScenarioRunnerSpec.scala (5), ProcessService.scala (3). — One of this dimension's main actionable groups (73 warning-level).
- Resolve the 1 TodoComment repeated across 14 files finding(s) in Explicit Debt — start with TestResultSinkFactory.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 128 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 4 build units (npm, sbt) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
93 finding(s): 0 critical, 90 high, 3 medium, 0 low. 68 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 10 file(s) — `components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala`, `designer/client/src/components/MenuBar/useStateWithRevertTimeout.tsx` (lines 3–18), `designer/client/src/components/graph/node-modal/BaseBuilderFieldWrapper.tsx` (line 27), `designer/client/src/components/graph/node-modal/fragment-input-definition/TypeSelect.tsx` (line 56, line 58, line 59, …), `designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala`, … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 68 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (68 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
150 finding(s): 13 critical, 91 high, 36 medium, 10 low.
What to do
- Resolve the 87 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (71), REDACTED (8), REDACTED (8). — One of this dimension's main actionable groups (87 issue-level).
- Resolve the 12 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED. — One of this dimension's main actionable groups (12 issue-level).
- Resolve the 4 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 1 high, 3 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D32 · Data Compliance (PII/GDPR)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 7 file(s) — `components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala`, `designer/client/src/components/MenuBar/useStateWithRevertTimeout.tsx`, `designer/client/src/components/graph/node-modal/BaseBuilderFieldWrapper.tsx`, `designer/client/src/components/graph/node-modal/fragment-input-definition/TypeSelect.tsx`, `designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala`, … (+2 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
What to do
- Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
463 of 1017 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala. Counted over 1017 of the 2649 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 462 Orphaned file finding(s) in Knowledge Freshness — start with DeploymentService.scala (2), types.ts (2), MethodDefinition.scala (2). — One of this dimension's main actionable groups (462 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with SpelExpressionSuggester.scala. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: GenericSourceWithCustomTestingSupport.scala↔SampleNodes.scala 100%; nodeDetails.ts↔nodeDetailsState.ts 90%; Interpreter.scala↔LoggingListener.scala 80%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with Interpreter.scala, GenericSourceWithCustomTestingSupport.scala. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 7 Change coupling finding(s) in Change Coupling — start with GenericSourceWithCustomTestingSupport.scala, nodeDetails.ts, TableSource.scala. — One of this dimension's main actionable groups (7 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — designer/client/src/components/graph/markups/bounding.html:2
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×9) — designer/client/src/components/common/DropdownButton.tsx:58, designer/client/src/components/dataMapper/FieldRow.tsx:299, designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx:107, …
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — designer/client/src/components/common/DropdownButton.tsx:128, designer/client/src/components/themed/InputWithIcon.tsx:92
- This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×9) — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:175, designer/client/src/components/conditionBuilder/ConditionRow.tsx:128, designer/client/src/components/dataMapper/DataMapper.tsx:165, …
- This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×3) — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:237, designer/client/src/components/conditionBuilder/ConditionRow.tsx:111, designer/client/src/components/dataMapper/FieldRow.tsx:328
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — designer/client/src/components/graph/node-modal/editors/expression/Duration/TimeRangeComponent.tsx:71, designer/client/src/components/sidePanels/SearchLabeledInput.tsx:14
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — designer/client/src/containers/DynamicTab.tsx:82
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×3) — designer/client/src/components/common/DropdownButton.tsx:128, designer/client/src/components/themed/InputWithIcon.tsx:92, designer/client/src/components/toolbars/creator/Tool.tsx:74
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 579 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with cypress-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
- `ListenerScenarioWithDetails` declares 21 abstract members: `name`, `processId`, `processVersionId`, `isLatestVersion`, `description`, `isArchived`, `isFragment`, `processingType`, `processCategory`, `modificationDate`, `modifiedAt`, `modifiedBy`, `createdAt`, `createdBy`, `scenarioLabels`, `lastDeployedAction`, `lastStateAction`, `lastAction`, `scenarioGraph`, `history`, `modelVersion`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — designer/listener-api/src/main/scala/pl/touk/nussknacker/ui/listener/ListenerScenarioWithDetails.scala:9
- `ProcessService` declares 18 abstract members: `getProcessIdUnsafe`, `getProcessId`, `getLatestProcessWithDetails`, `getProcessWithDetails`, `getLatestProcessesWithDetails`, `getLatestVersionForProcesses`, `getLatestRawProcessesWithDetails`, `getScenarioGraphsForVersionIds`, `archiveProcess`, `deleteProcess`, `unArchiveProcess`, `renameProcess`, `createProcess`, `updateProcess`, `updateProcessDBIO`, `migrateProcess`, `importProcess`, `getProcessActions`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — designer/server/src/main/scala/pl/touk/nussknacker/ui/process/ProcessService.scala:129
- `PeriodicProcessesRepository` declares 20 abstract members: `run`, `markInactive`, `getSchedulesState`, `create`, `getLatestDeploymentsForActiveSchedules`, `getLatestDeploymentsForActiveSchedules`, `getLatestDeploymentsForLatestInactiveSchedules`, `getLatestDeploymentsForLatestInactiveSchedules`, `findToBeDeployed`, `findToBeRetried`, `findActiveSchedulesForProcessesHavingDeploymentWithMatchingStatus`, `findProcessData`, `markDeployed`, `markFinished`, `markFailedOnDeployWithStatus`, `markFailed`, `schedule`, `fetchInputConfigDuringExecutionJson`, `fetchCanonicalProcess`, `fetchProcessVersion`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. Those 20 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/PeriodicProcessesRepository.scala:82
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- `setLogWriter` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:39
- `getLoginTimeout` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:41
- `setLoginTimeout` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:43
- `getParentLogger` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:45
- `getLogWriter` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:47
- `exampleOfType` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:47
- `getFieldA` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:82
- `addFieldA` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:102
- `zip` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:123
- `invoke` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/CollectionTypesService.scala:10, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/DatesTypesService.scala:14, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/SimpleTypesService.scala:14
- `implementation` is a shipped member whose whole body is still `???`, and nothing in the repository overrides it — generated scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/HidingVariablesTransformer.scala:32
- A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. (×3) — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:22, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:46, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:62
What to do
- Finish or delete the members whose body is still `???` or a "not implemented" throw where nothing overrides them, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `AlwaysUsingSameConnectionDataSource` has 5 unfinished members out of 9 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:9
- `setLogWriter` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:39
- `getLoginTimeout` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:41
- `setLoginTimeout` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:43
- `getParentLogger` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:45
- `getLogWriter` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:47
- `ExampleFunctions` has 4 unfinished members out of 5 declared methods (whether or not each carries a body) — a scaffolded class that was never implemented. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:25
- `exampleOfType` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:47
- `getFieldA` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:82
- `addFieldA` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:102
- `zip` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:123
- `invoke` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. (×3) — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/CollectionTypesService.scala:10, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/DatesTypesService.scala:14, engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/SimpleTypesService.scala:14
- `implementation` is a shipped method whose whole body is `???` (or throws NotImplementedError), and nothing in the repository overrides it — scaffolding that was never completed. Implement it or remove the dead surface. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/HidingVariablesTransformer.scala:32
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×9) — designer/server/src/test/scala/pl/touk/nussknacker/ui/api/ProcessesResourcesSpec.scala:261, designer/server/src/test/scala/pl/touk/nussknacker/ui/api/ProcessesResourcesSpec.scala:399, designer/server/src/test/scala/pl/touk/nussknacker/ui/config/ConfigurationTest.scala:79, …
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)
- 162 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 3 project(s) that lack one — worth up to 0.7 pts.
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md links to `./docs/NuHighLevelView.png`, but `docs/NuHighLevelView.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:61
- CONTRIBUTING/README.md links to `docs/installation_configuration_guide/README.md`, but `CONTRIBUTING/docs/installation_configuration_guide/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING/README.md:58
- CONTRIBUTING/README.md links to `designer/client/README.md`, but `CONTRIBUTING/designer/client/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING/README.md:205
- designer/client/README.md links to `../../CONTRIBUTING.md#running`, but `CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — designer/client/README.md:37
What to do
- Reconcile the README with reality: README.md links to `./docs/NuHighLevelView.png`, but `docs/NuHighLevelView.png` does not exist; CONTRIBUTING/README.md links to `docs/installation_configuration_guide/README.md`, but `CONTRIBUTING/docs/installation_configuration_guide/README.md` does not exist; CONTRIBUTING/README.md links to `designer/client/README.md`, but `CONTRIBUTING/designer/client/README.md` does not exist; designer/client/README.md links to `../../CONTRIBUTING.md#running`, but `CONTRIBUTING.md` does not exist.
P1 · CI/CD gates
P10 · Library API & versioning
- 55/62 types (89%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.
P2 · Observability
- Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `designer/client`.
- `engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-es-bundle-core.js` reports through `console.*` at line 2 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-es-bundle-core.js:2
- `engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-standalone-preset.js` reports through `console.*` at line 2 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-standalone-preset.js:2
- `engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui.js:1
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `axios.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — designer/client/src/api.ts:7
What to do
- Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
P8 · Schema migrations
PF1 · Benchmark discipline
- A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — benchmarks/src/test/scala/pl/touk/nussknacker/engine/benchmarks/suggester/ExpressionSuggesterBenchmark.scala
What to do
- Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 91 use(s) across 134,496 production line(s) (~0.7/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Scala: on hot paths, make small wrappers value classes (extends AnyVal), @specialized generic code over primitives, use primitive collections, and presize builders.
PF3 · Async & latency hygiene
- `invoke` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MeetingService.scala:17
- `waitForSavepoint` is async and calls Thread.sleep — a blocking call inside async code stalls the execution-context thread, and every future or fiber scheduled on it for as long as it runs. — engine/flink/management/src/main/scala/pl/touk/nussknacker/engine/management/rest/HttpFlinkClient.scala:126
What to do
- Scala: compose the Future or effect (map/flatMap, a for-comprehension) instead of Await.result or unsafeRunSync, and wrap unavoidable blocking calls in blocking { } (Future), IO.blocking or ZIO.attemptBlocking.
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 19 duplicated blocks under designer/client/src/components/ have copies in at least two of the sibling directories conditionBuilder, dataMapper, graph, modals, spelExpressionBuilder, tips (+1 more sibling(s) not listed) — 16 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164
- 13 duplicated blocks under designer/client/src/components/toolbars/ have copies in at least two of the sibling directories creator, edit, process, scenarioActions, search, view — 3 of them are reported below, and 10 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — designer/client/src/components/toolbars/process/buttons/SaveButton.tsx:58
- 10 duplicated blocks under designer/submodules/packages/components/src/ have copies in at least two of the sibling directories common, components, scenarios — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34
- 7 duplicated blocks under designer/ have copies in at least two of the sibling directories client, submodules — 6 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — designer/client/configs/simpleScriptPlugin.ts:8
- 6 duplicated blocks under designer/client/src/components/graph/node-modal/ have copies in at least two of the sibling directories aggregate, editors, fragment-input-definition, node, node-action-buttons — 2 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62
- designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:113 · designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:142 — the two spans are one implementation copied and then locally edited — 543 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:113
- designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:83 · designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:81 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:83
- designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164 · designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:151 — the two spans are one implementation copied and then locally edited — 632 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164
- designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34 · designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:23 — the two spans are one implementation copied and then locally edited — 555 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34
- designer/client/src/components/graph/node-modal/editors/expression/Duration/DurationEditor.tsx:32 · designer/client/src/components/graph/node-modal/editors/expression/Duration/PeriodEditor.tsx:28 — the two spans are one implementation copied and then locally edited — 320 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — designer/client/src/components/graph/node-modal/editors/expression/Duration/DurationEditor.tsx:32
- designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16 · designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/FixedListVariant.tsx:15 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16
- designer/client/configs/simpleScriptPlugin.ts:8 · designer/submodules/configs/webpack/simpleScriptPlugin.ts:8 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — designer/client/configs/simpleScriptPlugin.ts:8
- designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:63 · designer/client/src/components/graph/EspNode/stickyNote/basicStickyNoteConfig.ts:63 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:63
- designer/client/src/http/HttpService/HttpService.ts:263 · designer/client/src/http/HttpService/HttpService.ts:311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — designer/client/src/http/HttpService/HttpService.ts:263
- designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:25 · designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:25 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:25
- designer/client/src/components/notifications/copyTooltip.tsx:15 · designer/submodules/packages/components/src/scenarios/list/copyTooltip.tsx:31 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/notifications/copyTooltip.tsx:15
- designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:14 · designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16 — the two spans are one implementation copied and then locally edited — 226 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:14
- designer/client/src/http/HttpService/HttpService.ts:927 · designer/client/src/http/HttpService/HttpService.ts:1075 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — designer/client/src/http/HttpService/HttpService.ts:927
- designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:159 · designer/client/src/components/graph/EspNode/stickyNote/basicStickyNoteConfig.ts:149 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:159
- designer/client/src/components/graph/node-modal/DescriptionField.tsx:10 · designer/client/src/components/graph/node-modal/DisableField.tsx:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — designer/client/src/components/graph/node-modal/DescriptionField.tsx:10
- designer/client/src/components/modals/DeployProcessDialog.tsx:46 · designer/client/src/components/modals/DeployWithParameters/DeployWithParametersDialog.tsx:48 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/modals/DeployProcessDialog.tsx:46
- designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx:35 · designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:27 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx:35
- designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateTimeEditor.tsx:16 · designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/TimeEditor.tsx:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateTimeEditor.tsx:16
- designer/client/src/components/modals/AddCommentDialog.tsx:28 · designer/client/src/components/modals/saveScenario/SaveScenarioDialog.tsx:22 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/modals/AddCommentDialog.tsx:28
- designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:60 · designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:126 · designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:150 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:60
- designer/client/src/components/conditionBuilder/ConditionRow.tsx:86 · designer/client/src/components/conditionBuilder/ConditionRow.tsx:136 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — designer/client/src/components/conditionBuilder/ConditionRow.tsx:86
- designer/client/src/components/graph/node-modal/FragmentOutputDefinition.tsx:25 · designer/client/src/components/graph/node-modal/MapVariable.tsx:30 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — designer/client/src/components/graph/node-modal/FragmentOutputDefinition.tsx:25
- designer/client/src/components/modals/GenerateDataAndTestDialog.tsx:38 · designer/client/src/components/modals/GenerateTestDataDialog.tsx:41 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/modals/GenerateDataAndTestDialog.tsx:38
- designer/client/src/components/dataMapper/dataMapperUtils.ts:339 · designer/client/src/components/graph/node-modal/ParametersUtils.ts:30 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — designer/client/src/components/dataMapper/dataMapperUtils.ts:339
- designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62 · designer/client/src/components/graph/node-modal/fragment-input-definition/TypeSelect.tsx:107 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62
- designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx:6 · designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:123 — the two spans are one implementation copied and then locally edited — 216 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx:6
- designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:45 · designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:45
- designer/client/src/common/copyToClipboard/useCopyToClipboard.ts:5 · designer/submodules/packages/components/src/scenarios/list/copyTooltip.tsx:7 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — designer/client/src/common/copyToClipboard/useCopyToClipboard.ts:5
- designer/client/configs/withModuleFederationPlugins.ts:64 · designer/submodules/configs/webpack/withModuleFederationPlugins.ts:119 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — designer/client/configs/withModuleFederationPlugins.ts:64
- designer/client/src/components/toolbars/scenarioActions/buttons/CancelDeployButton.tsx:78 · designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:146 · designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:144 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/toolbars/scenarioActions/buttons/CancelDeployButton.tsx:78
- designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:65 · designer/client/src/components/dataMapper/useDataMapper.ts:292 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:65
- designer/client/src/components/dataMapper/dataMapperUtils.ts:215 · designer/client/src/components/dataMapper/dataMapperUtils.ts:239 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/dataMapper/dataMapperUtils.ts:215
- designer/submodules/packages/components/src/components/usages/usagesTable.tsx:206 · designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:159 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/submodules/packages/components/src/components/usages/usagesTable.tsx:206
- designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:99 · designer/client/src/components/graph/EspNode/stickyNote/basicStickyNoteConfig.ts:99 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:99
- designer/client/src/components/graph/node-modal/DescriptionField.tsx:23 · designer/client/src/components/graph/node-modal/DisableField.tsx:22 · designer/client/src/components/graph/node-modal/sink.tsx:21 · designer/client/src/components/graph/node-modal/source.tsx:20 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — designer/client/src/components/graph/node-modal/DescriptionField.tsx:23
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- designer/client/configs/withModuleFederationPlugins.ts:9 imports webpack/lib/util/extractUrlAndGlobal, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/configs/withModuleFederationPlugins.ts:9
- designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:10 imports designer/client/src/components/toolbars/test/buttons/ButtonProgress.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:10
- designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:11 imports designer/client/src/components/toolbars/test/buttons/useProgress.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:11
- designer/client/src/components/graph/node-modal/editors/expression/ExpressionField.tsx:10 imports designer/client/src/components/graph/node-modal/tests/ExpressionTestResults.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/graph/node-modal/editors/expression/ExpressionField.tsx:10
- designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:1 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../invariant, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:1
- designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:8 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../event-bindings/bind-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:8
- designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:15 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../key-codes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:15
- designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:16 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../use-isomorphic-layout-effect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:16
- designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:17 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/prevent-standard-key-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:17
- designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:18 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/supported-page-visibility-event-name, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:18
- designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:1 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../empty, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:1
- designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:2 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../invariant, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:2
- designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:10 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../event-bindings/bind-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:10
- designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:18 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../key-codes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:18
- designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:19 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../use-isomorphic-layout-effect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:19
- designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:20 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/prevent-standard-key-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:20
- designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:21 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/supported-page-visibility-event-name, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:21
- designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../empty, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1
- designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:2 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../../invariant, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:2
- designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:9 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../event-bindings/bind-events, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:9
- designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:16 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../key-codes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:16
- designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:17 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/../../use-isomorphic-layout-effect, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:17
- designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:18 imports @hello-pangea/dnd/src/view/use-sensor-marshal/sensors/util/supported-page-visibility-event-name, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:18
- designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:6 imports designer/client/src/components/toolbars/test/buttons/ButtonProgress.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:6
- designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:23 imports designer/client/src/components/toolbars/test/buttons/AdhocTestingButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:23
- designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:24 imports designer/client/src/components/toolbars/test/buttons/CountsButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:24
- designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:25 imports designer/client/src/components/toolbars/test/buttons/FromFileButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:25
- designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:26 imports designer/client/src/components/toolbars/test/buttons/GenerateAndTestButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:26
- designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:27 imports designer/client/src/components/toolbars/test/buttons/GenerateButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:27
- designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:28 imports designer/client/src/components/toolbars/test/buttons/HideButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:28
- designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:29 imports designer/client/src/components/toolbars/test/buttons/LiveDataButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:29
- designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:30 imports designer/client/src/components/toolbars/test/buttons/ScenarioTestButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:30
- designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:31 imports designer/client/src/components/toolbars/test/buttons/SnowSnowButton.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:31
- designer/client/src/components/toolbarSettings/getToolbarComponent.ts:35 imports designer/client/src/components/toolbars/testCases/testCasesPanel.tsx, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — designer/client/src/components/toolbarSettings/getToolbarComponent.ts:35
- designer/client/src/reducers/notifications.ts:3 imports redux-persist/lib/storage, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/reducers/notifications.ts:3
- designer/client/src/reducers/toolbars.ts:3 imports redux-persist/lib/storage, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/reducers/toolbars.ts:3
- designer/client/src/reducers/userSettings.ts:2 imports redux-persist/lib/storage, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/client/src/reducers/userSettings.ts:2
- designer/submodules/configs/webpack/common.ts:8 reaches into another package with a relative path (../../../client/version) — import the package by name instead. — designer/submodules/configs/webpack/common.ts:8
- designer/submodules/configs/webpack/withModuleFederationPlugins.ts:7 imports webpack/lib/util/extractUrlAndGlobal, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — designer/submodules/configs/webpack/withModuleFederationPlugins.ts:7
- designer/submodules/configs/webpack/withModuleFederationPlugins.ts:9 reaches into another package with a relative path (../../../client/version) — import the package by name instead. — designer/submodules/configs/webpack/withModuleFederationPlugins.ts:9
What to do
- Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (26 rows); move the shared test helper into a source directory production code may depend on (14 rows).
R2 · Cyclomatic Complexity
- FieldRow has cyclomatic complexity 40 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/dataMapper/FieldRow.tsx:90
- ContextTreeNode has cyclomatic complexity 36 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/builderComponents/ContextTreeNode.tsx:50
- (anonymous) has cyclomatic complexity 26 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/modals/TestingDataRecords/drawText.ts:141
- (anonymous) has cyclomatic complexity 22 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/dataMapper/useDataMapper.ts:197
- (anonymous) has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/common/ProcessUtils.ts:148
- DataMapper has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/dataMapper/DataMapper.tsx:68
- ToolbarWrapper has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/toolbarComponents/toolbarWrapper/ToolbarWrapper.tsx:33
- buildFragmentsForTokens has cyclomatic complexity 18 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/modals/TestingDataRecords/drawText.ts:120
- parseConditionAst has cyclomatic complexity 17 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/conditionBuilder/spelUtils.ts:64
- typingResultToSample has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/builderComponents/typeUtils.ts:12
- VariantWrapper has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/toolbarComponents/toolbarButtons/ButtonRoot.tsx:12
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:107
- adjustEdges has cyclomatic complexity 16 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:50
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/modals/TestingDataRecords/drawText.ts:70
- refClazzToValue has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — designer/client/src/components/graph/node-modal/Variable.tsx:42
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- designer/client/src/http/HttpService/HttpService.ts has 1226 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/http/HttpService/HttpService.ts:1
- designer/client/src/components/graph/Graph.tsx has 743 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/graph/Graph.tsx:1
- designer/client/src/components/dataMapper/useDataMapper.ts has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/dataMapper/useDataMapper.ts:1
- designer/client/src/components/modals/CompareVersionsDialog.tsx has 569 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/modals/CompareVersionsDialog.tsx:1
- designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx has 530 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:1
- designer/client/src/reducers/graph/reducer.ts has 501 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/reducers/graph/reducer.ts:1
- designer/client/src/components/dataMapper/FieldRow.tsx has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/dataMapper/FieldRow.tsx:1
- designer/client/src/components/dataMapper/dataMapperUtils.ts has 452 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/dataMapper/dataMapperUtils.ts:1
- designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1
- designer/client/src/components/dataMapper/DataMapper.tsx has 417 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — designer/client/src/components/dataMapper/DataMapper.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — designer/client/src/components/graph/Graph.tsx:1, designer/client/src/reducers/graph/reducer.ts:1, designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 158 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Unreachable from the 40 application, 10 tooling and 126 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/toolbars/scenarioDetails/ScenarioDetails.tsx, designer/client/src/components/toolbars/scenarioDetails/ScenarioStatusContent.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx, designer/client/src/components/toolbars/search/SearchResults.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/search/utils.ts
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/RootRoutes.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/Visualization.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbars/Toolbars.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbarComponents/ToolbarsLayer.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbarSettings/getToolbarComponent.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/creator/CreatorPanel.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/WindowManager.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/windowManager/ContentGetter.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/modals/CalculateCounts/CountsStyled.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/common/DropdownButton.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×5) — designer/client/src/components/AddProcessDialog.tsx, designer/client/src/components/graph/node-modal/node/DescriptionDialog.tsx, designer/client/src/components/modals/MoreScenarioDetailsDialog.tsx, …
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/MenuBar/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — designer/client/src/components/MenuBar/menu.tsx, designer/client/src/components/MenuBar/breadcrumbs.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Visualization.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×5) — designer/client/src/containers/liveData/LiveDataThroughputs.tsx, designer/client/src/containers/ScenarioDescription.tsx, designer/client/src/components/aiAssistant/tools/ScenarioDataAIToolkit.tsx, …
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbars/search/SearchPanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/aiAssistant/ModelAdapter.ts, designer/client/src/components/aiAssistant/debug/MockAssitantFetch.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/aiAssistant/InitializeChatStream.ts
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/Auth/strategies/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/Auth/strategies/OAuth2Strategy.ts
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/components/AiAssistantModal.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — designer/client/src/components/aiAssistant/components/Composer.tsx, designer/client/src/components/aiAssistant/components/AssistantMessage.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/modals/CalculateCounts/CalculateCountsForm.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/modals/CalculateCounts/RefreshSelectButton.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/modals/DeployWithParameters/DeployWithParametersDialog.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/modals/DeployWithParameters/AdvancedParameters.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (designer/client/src/components/SidePanelToggleButton.tsx, designer/client/src/components/sidePanels/SidePanel.tsx, designer/client/src/components/toolbarComponents/ToolbarsLayer.tsx and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/sidePanels/SidePanelsContext.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/toolbars/creator/CreatorPanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/NodeCreationHandler.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/AiAssistantProvider.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/aiAssistant/ModelAdapter.ts
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/liveData/LiveDataThroughputs.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/liveData/animationHelpers.ts
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 4 in-repo import(s) from 3 other file(s) do name it (designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx, designer/client/src/components/toolbars/search/SearchPanel.tsx, designer/client/src/components/toolbars/search/utils.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/toolbars/search/SearchResults.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/containers/NussknackerApp.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/versionInfo.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/CommandBar/settings/useRegisterSettingsCommands.tsx, designer/client/src/containers/RootRoutes.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/containers/settings/SettingsView.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (designer/client/src/components/modals/CalculateCounts/CalculateCountsForm.tsx, designer/client/src/windowManager/ContentGetter.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/modals/CalculateCounts/CalculateCountsDialog.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — designer/client/configs/withModuleFederationPlugins.ts
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/aiAssistant/InitializeChatStream.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — designer/client/src/components/aiAssistant/messageHelpers.ts, designer/client/src/components/aiAssistant/debug/MockAssitantFetch.ts
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/sidePanels/CollapsibleScrollPanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/sidePanels/CollapsiblePanel.tsx
- no import path from any entry point (40 application, 10 tooling, 126 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (designer/client/src/components/tips/Tips.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — designer/client/src/components/tips/Warnings.tsx
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. (×4) — designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:1, designer/client/src/components/graph/node-modal/io/PanelButton.tsx:2, designer/client/src/components/aiAssistant/useCheckPermission.tsx:1, …
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×7) — designer/client/jest-setup.js:2, designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/useMockEnabled.ts:1, designer/client/src/components/graph/PanZoomPlugin.ts:2, …
- Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
- Every import is type-only — move it to devDependencies. — designer/client/src/actions/notificationActions.tsx:5
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- designer/client/src/actions/nk/editNode.ts → designer/client/src/components/graph/node-modal/node/useNodeState.tsx → designer/client/src/actions/nk/editNode.ts — designer/client/src/actions/nk/editNode.ts:4
- designer/client/src/actions/nk/liveData.ts → designer/client/src/actions/nk/process.ts → designer/client/src/actions/nk/liveData.ts — designer/client/src/actions/nk/liveData.ts:10
- designer/client/src/actions/nk/nodeDetails.ts → designer/client/src/actions/nk/validationsActions.ts → designer/client/src/actions/nk/nodeDetails.ts — designer/client/src/actions/nk/nodeDetails.ts:12
- designer/client/src/actions/nk/testCasesActions.ts → designer/client/src/actions/nk/testingActions.ts → designer/client/src/reducers/selectors/testCases.ts → designer/client/src/components/graph/node-modal/editors/expression/MockExpressionField.tsx → designer/client/src/actions/nk/testCasesActions.ts — designer/client/src/actions/nk/testCasesActions.ts:14
- designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx → designer/client/src/components/toolbarComponents/toolbarButtons/ButtonMenu.tsx → designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx (one verified cycle inside a mutually-dependent group of 53 files) — designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:7
- designer/client/src/common/CodeBlock.tsx → designer/client/src/common/copyToClipboard/CopyIconButton.tsx → designer/client/src/components/graph/node-modal/editors/InfoTooltip/InfoTooltip.tsx → designer/client/src/components/graph/node-modal/editors/InfoTooltip/StyledInfoMarkdown.tsx → designer/client/src/components/graph/node-modal/MarkdownStyled.tsx → designer/client/src/components/graph/node-modal/MarkdownWithPlugins.tsx → designer/client/src/common/CodeBlock.tsx (one verified cycle inside a mutually-dependent group of 8 files) — designer/client/src/common/CodeBlock.tsx:7
- designer/client/src/components/ValueDragPreview.tsx → designer/client/src/components/graph/node-modal/editors/expression/useAceDndTarget.tsx → designer/client/src/components/ValueDragPreview.tsx — designer/client/src/components/ValueDragPreview.tsx:11
- designer/client/src/components/graph/EspNode/element.ts → designer/client/src/components/graph/EspNode/esp.ts → designer/client/src/components/graph/EspNode/element.ts (one verified cycle inside a mutually-dependent group of 11 files) — designer/client/src/components/graph/EspNode/element.ts:15
- designer/client/src/components/graph/Graph.tsx → designer/client/src/components/graph/utils/dragHelpers.ts → designer/client/src/components/graph/Graph.tsx — designer/client/src/components/graph/Graph.tsx:49
- designer/client/src/components/graph/NodeUtils.ts → designer/client/src/reducers/graph/utils.ts → designer/client/src/components/graph/NodeUtils.ts (one verified cycle inside a mutually-dependent group of 3 files) — designer/client/src/components/graph/NodeUtils.ts:7
- designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx → designer/client/src/components/graph/node-modal/tests/TestErrors.tsx → designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx (one verified cycle inside a mutually-dependent group of 3 files) — designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx:12
- designer/client/src/components/graph/node-modal/editors/expression/Editor.ts → designer/client/src/components/graph/node-modal/editors/expression/BoolEditor.tsx → designer/client/src/components/graph/node-modal/editors/expression/Editor.ts (one verified cycle inside a mutually-dependent group of 26 files) — designer/client/src/components/graph/node-modal/editors/expression/Editor.ts:6
- designer/client/src/components/graph/node-modal/editors/map/Map.tsx → designer/client/src/components/graph/node-modal/editors/map/MapRow.tsx → designer/client/src/components/graph/node-modal/editors/map/Map.tsx — designer/client/src/components/graph/node-modal/editors/map/Map.tsx:11
- designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx → designer/client/src/components/graph/node-modal/node-row-fields-provider/buttons/AddButton.tsx → designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx — designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx:4
- designer/client/src/components/toolbars/creator/ToolBox.tsx → designer/client/src/components/toolbars/creator/ToolboxCommands.tsx → designer/client/src/reducers/selectors/getFilteredComponentGroups.ts → designer/client/src/components/toolbars/creator/ToolBox.tsx — designer/client/src/components/toolbars/creator/ToolBox.tsx:16
- designer/client/src/reducers/graph/historySquash.ts → designer/client/src/reducers/graph/reducer.ts → designer/client/src/reducers/graph/historySquash.ts — designer/client/src/reducers/graph/historySquash.ts:6
- designer/submodules/packages/components/src/components/usages/nodesCell.tsx → designer/submodules/packages/components/src/components/usages/usagesTable.tsx → designer/submodules/packages/components/src/components/usages/nodesCell.tsx — designer/submodules/packages/components/src/components/usages/nodesCell.tsx:14
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`MessageDigest.getInstance("SHA-256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×3) — engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:169, engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:214, engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/UberJarAssembler.scala:40
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — examples/installation/nginx/nginx.conf:2
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:169` (MessageDigest.getInstance("SHA-1")), `engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:214` (MessageDigest.getInstance("SHA-1")), `engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/UberJarAssembler.scala:40` (MessageDigest.getInstance("SHA-1")). Each is a separate decision — fixing only the line this row cites leaves the others in place.
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `JsonSchemaUtils.circeToJson` is public and takes `value: Json` from its caller, and it calls itself at line 19 with a piece of `value` (and at line 20), not as a tail call the compiler turns into a loop — and nowhere in `JsonSchemaUtils.circeToJson` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `JsonSchemaUtils.circeToJson` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/util/json/JsonSchemaUtils.scala:19
- `jsonToSpelString` is exported and takes `value: any` from its caller, and it calls itself at line 22 (`jsonToSpelString`) with a piece of `value` (and at line 26) — and nowhere in `jsonToSpelString` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `jsonToSpelString` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/graph/node-modal/editors/expression/useAceDndTarget.tsx:22
- `fieldsFromSample` is exported and takes `obj: unknown` from its caller, and it calls itself at line 331 (`fieldsFromSample`) with a piece of `obj` — and nowhere in `fieldsFromSample` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `fieldsFromSample` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/dataMapper/dataMapperUtils.ts:331
- `inferDisplayType` is exported and takes `val: unknown` from its caller, and it calls itself at line 6 (`inferDisplayType`) with a piece of `val` — and nowhere in `inferDisplayType` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `inferDisplayType` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/builderComponents/typeUtils.ts:6
- `typingResultToSample` is exported and takes `t: any` from its caller, and it calls itself at line 16 (`typingResultToSample`) with a piece of `t` (and at line 21) — and nowhere in `typingResultToSample` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `typingResultToSample` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/builderComponents/typeUtils.ts:16
- `treeNodeMatchesFilter` is exported and takes `value: unknown` from its caller, and it calls itself at line 40 (`treeNodeMatchesFilter`) with a piece of `value` — and nowhere in `treeNodeMatchesFilter` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `treeNodeMatchesFilter` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — designer/client/src/components/builderComponents/typeUtils.ts:40
- `FromJsonSimpleDecoder.jsonToAny` is public and takes `json: Json` from its caller, and it calls itself at line 15 with a piece of `json` (and at line 19), not as a tail call the compiler turns into a loop — and nowhere in `FromJsonSimpleDecoder.jsonToAny` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. On the JVM's default 1 MB thread stack a walk like this one throws `StackOverflowError` from about 500–2,000 levels on a cold first call and 6,000–17,000 once warmed up (OpenJDK 21 and 25), while `ujson.read`, Jackson's `readTree` before 2.15 and circe before 0.14.16 accept any nesting (2,000,000 levels from 4 MB) and circe 0.14.16 accepts 4,096 — on a cold JVM even play-json's cap of 1,000 is past the point the walk fails. `StackOverflowError` is not `NonFatal`: `Try`, `case NonFatal(e)` and `recover` do not stop it, and in a `Future` on the global execution context it leaves the future forever incomplete. Thread a depth argument through `FromJsonSimpleDecoder.jsonToAny` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/decoders/FromJsonSimpleDecoder.scala:15
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `read` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — designer/submodules/packages/components/src/settings/i18n.ts:16
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `id` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:53
- `` * { cursor: ${cursor} !important; } html, body, * { …` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — designer/client/src/components/graph/GlobalCursor.ts:10
- `truncatedElement.innerHTML` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — designer/client/src/components/graph/node-modal/editors/expression/LineClamp.tsx:106
- `svgString` is text this program did not author, and it is written into the text of an element through `document.write` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — designer/client/src/components/graph/svg-export/prepareSvg.ts:17
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `case t: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassSerializer.scala:69
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×8) — designer/client/src/windowManager/LoadingButton.tsx:19, designer/client/src/store/draftListener.ts:179, REDACTED:38, …
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×3) — designer/client/src/store/draftListener.ts:101, designer/client/src/store/draftListener.ts:129, designer/client/src/components/graph/SelectionContextProvider.tsx:96
- `.catch((e) => {return;})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:340
- `.catch(() => {return;})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:454
- `catch (error)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — designer/client/src/components/modals/saveScenario/useSaveScenario.ts:79
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error` at line 46 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — live-data-collector/src/main/scala/pl/touk/nussknacker/engine/livedata/LiveDataUploader.scala:46
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 1575 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 47% | Weak — gated by R7, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 57% | Adequate — gated by D26, R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 51% | Adequate — gated by M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 37% | Weak — gated by R5, R8, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by D29, D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 27% | Weak — gated by AC1, AC2, AC3, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 72% | Strong | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 37 check(s) not relevant to this codebase
- AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — kafka Error Get "https://registry-1.docker.io/v2/": Forbidden grafana Error context canceled telegraf Error context canceled postgres Error context canceled nginx Error context canceled influxdb Error context canceled akhq Error context canceled designer Error context canceled schema-registry Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: grafana Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error context canceled kafka Error context canceled akhq Error context canceled schema-registry Error context canceled telegraf Error context canceled influxdb Error context canceled designer Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, JavaScript, Scala, TypeScript, html not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .scala, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
- DM1 Domain Modelling — applicable but not scored (4 signals for this style, 2 needed — the count is met but a required primary signal is absent): 7 strongly-typed id(s); 328 value object(s); 31 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — coverage data present for 344 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 236 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) designer/client/src/actions/nk/editNode.ts:4
- Import cycle (2 files) designer/client/src/actions/nk/liveData.ts:10
- Import cycle (2 files) designer/client/src/actions/nk/nodeDetails.ts:12
- Import cycle (2 files) designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:7
- Import cycle (2 files) designer/client/src/components/ValueDragPreview.tsx:11
- Import cycle (2 files) designer/client/src/components/graph/EspNode/element.ts:15
- Import cycle (2 files) designer/client/src/components/graph/Graph.tsx:49
- Import cycle (2 files) designer/client/src/components/graph/NodeUtils.ts:7
- Import cycle (2 files) designer/client/src/components/graph/node-modal/TestResultsWrapper.tsx:12
- Import cycle (2 files) designer/client/src/components/graph/node-modal/editors/expression/Editor.ts:6
- Import cycle (2 files) designer/client/src/components/graph/node-modal/editors/map/Map.tsx:11
- Import cycle (2 files) designer/client/src/components/graph/node-modal/node-row-fields-provider/FieldsControl.tsx:4
- Import cycle (2 files) designer/client/src/reducers/graph/historySquash.ts:6
- Import cycle (2 files) designer/submodules/packages/components/src/components/usages/nodesCell.tsx:14
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <div> designer/client/src/components/common/DropdownButton.tsx:128
- Click handler on a non-interactive <div> designer/client/src/components/themed/InputWithIcon.tsx:92
- Click handler on a non-interactive <div> designer/client/src/components/toolbars/creator/Tool.tsx:74
- REDACTED
- REDACTED
- REDACTED
- Custom control with no accessible name on <div> designer/client/src/components/common/DropdownButton.tsx:128
- Custom control with no accessible name on <div> designer/client/src/components/themed/InputWithIcon.tsx:92
- <input> without a programmatic label designer/client/src/components/graph/node-modal/editors/expression/Duration/TimeRangeComponent.tsx:71
- <input> without a programmatic label designer/client/src/components/sidePanels/SearchLabeledInput.tsx:14
- REDACTED
- REDACTED
- Boundary-crossing change coupling: Interpreter.scala ↔ LoggingListener.scala scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala:1
- Boundary-crossing change coupling: GenericSourceWithCustomTestingSupport.scala ↔ KafkaContextInitializer.scala engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomTestingSupport.scala:1
- <img> without a text alternative designer/client/src/components/graph/markups/bounding.html:2
- <iframe> without a title designer/client/src/containers/DynamicTab.tsx:82
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala:1
- Unlisted import '@jest/globals' designer/client/jest-setup.js:2
- Unlisted import '@mui/utils' designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/useMockEnabled.ts:1
- Unlisted import 'd3-selection' designer/client/src/components/graph/PanZoomPlugin.ts:2
- Unlisted import 'use-memo-one' designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:20
- Unlisted import '@emotion/cache' designer/submodules/packages/components/src/settings/rootProviders.tsx:1
- Unlisted import '@mui/system' designer/submodules/packages/components/src/common/PlaceholderIconFallbackComponent.tsx:2
- Unlisted import 'stylis' designer/submodules/packages/components/src/settings/rootProviders.tsx:7
- Import cycle (4 files) designer/client/src/actions/nk/testCasesActions.ts:14
- Import cycle (6 files) designer/client/src/common/CodeBlock.tsx:7
- Import cycle (3 files) designer/client/src/components/toolbars/creator/ToolBox.tsx:16
Serious — 1299 finding(s)
- TodoComment utils/test-utils/src/main/scala/pl/touk/nussknacker/test/UniquePortProvider.scala:16
- TodoComment utils/schemed-kafka-components-utils/src/test/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/azure/AzureSchemaBasedSerdeProviderIntegrationTest.scala:58
- TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/KafkaUniversalComponentTransformer.scala:102
- TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/typed/AvroSchemaTypeDefinitionExtractor.scala:49
- TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:459
- TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/universal/RecordFormatterSupport.scala:45
- TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/universal/UniversalKafkaDeserializer.scala:63
- TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/confluent/serialization/jsonpayload/ConfluentJsonPayloadKafkaSerializer.scala:15
- TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schemaregistry/azure/SchemaNameTopicMatchStrategy.scala:9
- TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/schema/AvroSchemaBasedParameter.scala:144
- TodoComment utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/encode/ToAvroSchemaBasedEncoder.scala:206
- TodoComment utils/lite-components-testkit/src/main/scala/pl/touk/nussknacker/engine/lite/util/test/LiteNodeCompiler.scala:27
- TodoComment utils/flink-components-testkit/src/main/scala/pl/touk/nussknacker/engine/flink/util/test/FlinkNodeCompiler.scala:30
- TodoComment utils/lite-components-testkit/src/main/scala/pl/touk/nussknacker/engine/lite/util/test/LiteTestScenarioRunner.scala:69
- TodoComment utils/lite-components-testkit/src/main/scala/pl/touk/nussknacker/engine/lite/util/test/SynchronousLiteInterpreter.scala:43
- TodoComment utils/components-testkit/src/main/scala/pl/touk/nussknacker/engine/util/test/TestScenarioRunner.scala:93
- TodoComment utils/kafka-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/KafkaComponentsConfig.scala:20
- TodoComment utils/kafka-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/KafkaComponentsConfig.scala:71
- TodoComment utils/kafka-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/exception/KafkaJsonExceptionSerializationSchema.scala:180
- TodoComment utils/kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/source/InputMeta.scala:59
- TodoComment utils/kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/kafka/source/InputMeta.scala:60
- TodoComment utils/json-utils/src/test/scala/pl/touk/nussknacker/engine/json/SwaggerBasedJsonSchemaTypeDefinitionExtractorTest.scala:393
- TodoComment utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonDefaultExpressionDeterminer.scala:50
- TodoComment utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonSchemaBuilder.scala:13
- TodoComment utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonSchemaBuilder.scala:14
- FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:47
- FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:71
- FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:96
- FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:122
- FixmeComment utils/lite-components-testkit/src/test/scala/pl/touk/nussknacker/engine/lite/util/test/RequestResponseTestScenarioRunnerSpec.scala:148
- FixmeComment utils/http-utils/src/main/scala/pl/touk/nussknacker/http/backend/HttpClientConfig.scala:57
- FixmeComment scenario-compiler/src/test/scala/pl/touk/nussknacker/engine/compile/FragmentResolverSpec.scala:562
- FixmeComment scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala:501
- FixmeComment scenario-api/src/main/scala/pl/touk/nussknacker/engine/graph/evaluatedparam.scala:12
- FixmeComment engine/lite/runtime/src/main/scala/pl/touk/nussknacker/engine/lite/ScenarioInterpreterFactory.scala:382
- FixmeComment engine/lite/runtime/src/main/scala/pl/touk/nussknacker/engine/lite/TestRunner.scala:59
- FixmeComment engine/lite/runtime/src/main/scala/pl/touk/nussknacker/engine/lite/TestRunner.scala:151
- FixmeComment engine/lite/kafka/runtime/src/main/scala/pl/touk/nussknacker/engine/lite/kafka/KafkaProducerRecordsHandler.scala:125
- FixmeComment engine/lite/components-api/src/main/scala/pl/touk/nussknacker/engine/lite/api/utils/sinks.scala:54
- FixmeComment engine/lite/components/request-response/src/main/scala/pl/touk/nussknacker/engine/lite/components/requestresponse/CollectTransformer.scala:55
- FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:85
- FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:461
- FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:482
- FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:499
- FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:533
- FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:1112
- FixmeComment engine/lite/components/kafka-tests/src/test/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalAvroSchemaFunctionalTest.scala:1118
- FixmeComment engine/lite/components/kafka/src/main/scala/pl/touk/nussknacker/engine/lite/components/LiteKafkaUniversalSinkImplFactory.scala:36
- FixmeComment engine/flink/management/src/main/scala/pl/touk/nussknacker/engine/management/rest/HttpFlinkClient.scala:125
- FixmeComment engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/ConstantStateTransformer.scala:11
- Boundary violation [package:third-party-deep-import] designer/client/configs/withModuleFederationPlugins.ts:9
- Boundary violation [package:test-suite-dependency] designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:10
- Boundary violation [package:test-suite-dependency] designer/client/src/components/common/error-boundary/fallbackComponent/DialogErrorFallbackComponent.tsx:11
- Boundary violation [package:test-suite-dependency] designer/client/src/components/graph/node-modal/editors/expression/ExpressionField.tsx:10
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:1
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:8
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:15
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:16
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:17
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-keyboard-sensor.ts:18
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:1
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:2
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:10
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:18
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:19
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:20
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:21
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:2
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:9
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:16
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:17
- Boundary violation [package:third-party-deep-import] designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:18
- Boundary violation [package:test-suite-dependency] designer/client/src/components/toolbarComponents/toolbarButtons/ToolbarButton.tsx:6
- Boundary violation [package:test-suite-dependency] designer/client/src/components/toolbarSettings/buttons/buttonsMap.ts:23
- No test reaches this file designer/client/src/components/graph/Graph.tsx:1
- No test reaches this file designer/client/src/reducers/graph/reducer.ts:1
- No test reaches this file designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:1
- No test reaches this file designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItemHeader.tsx:1
- No test reaches this file designer/client/src/components/modals/TestingDataRecords/Table.tsx:1
- No test reaches this file designer/client/src/components/graph/RangeSelectPlugin.ts:1
- No test reaches this file designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/InputDataRecords.tsx:1
- No test reaches this file designer/client/src/components/toolbars/search/utils.ts:1
- No test reaches this file designer/client/src/containers/Visualization.tsx:1
- No test reaches this file designer/submodules/packages/components/src/components/usages/usagesTable.tsx:1
- No test reaches this file designer/client/src/components/AddProcessForm.tsx:1
- No test reaches this file designer/client/src/components/graph/node-modal/ParametersUtils.ts:1
- No test reaches this file designer/client/src/components/graph/NodeDescriptionPopover.tsx:1
- No test reaches this file designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx:1
- No test reaches this file designer/submodules/packages/components/src/components/listWithFilters.tsx:1
- No test reaches this file designer/client/src/components/toolbarComponents/ToolbarsLayer.tsx:1
- No test reaches this file designer/client/src/containers/settings/collapsibleSwitchList.tsx:1
- No test reaches this file designer/client/src/components/graph/node-modal/node/NodeDetails.tsx:1
- No test reaches this file designer/client/src/components/toolbars/activities/ActivitiesPanel.tsx:1
- No test reaches this file designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:1
- No test reaches this file designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItem.tsx:1
- No test reaches this file designer/client/src/components/toolbars/creator/ToolBox.tsx:1
- No test reaches this file designer/client/src/components/toolbars/creator/CreatorPanel.tsx:1
- No test reaches this file designer/client/src/components/graph/PanZoomPlugin.ts:1
- No test reaches this file designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/Assertions.tsx:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: useDataMapper.useDataMapper designer/client/src/components/dataMapper/useDataMapper.ts:139
- FunctionTooLong: FieldRow.FieldRow designer/client/src/components/dataMapper/FieldRow.tsx:90
- FunctionTooLong: DataMapper.DataMapper designer/client/src/components/dataMapper/DataMapper.tsx:68
- FunctionTooLong: CompareVersionsDialog.VersionsForm designer/client/src/components/modals/CompareVersionsDialog.tsx:159
- FunctionTooLong: TableEditor.Table designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:119
- FunctionTooLong: ConditionBuilder.ConditionBuilder designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:47
- FunctionTooLong: reducer.graphReducer designer/client/src/reducers/graph/reducer.ts:170
- FunctionTooLong: ScenarioLabels.ScenarioLabels designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:132
- FunctionTooLong: SpelExpressionBuilder.SpelExpressionBuilder designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:83
- FunctionTooLong: Table.Table designer/client/src/components/modals/TestingDataRecords/Table.tsx:56
- FunctionTooLong: InputDataRecords.InputDataRecords designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/InputDataRecords.tsx:33
- FunctionTooLong: Variable.Variable designer/client/src/components/graph/node-modal/Variable.tsx:82
- FunctionTooLong: AddProcessForm.AddProcessForm designer/client/src/components/AddProcessForm.tsx:39
- FunctionTooLong: NodeTypeDetailsContent.NodeDetails designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:48
- FunctionTooLong: usagesTable.UsagesTable designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34
- FunctionTooLong: ContextTreeNode.ContextTreeNode designer/client/src/components/builderComponents/ContextTreeNode.tsx:50
- FunctionTooLong: tablePart.TablePart designer/submodules/packages/components/src/scenarios/list/tablePart.tsx:23
- FunctionTooLong: DeployButton.DeployButton designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:33
- FunctionTooLong: EdgeFields.EdgeFields designer/client/src/components/graph/node-modal/EdgeFields.tsx:39
- FunctionTooLong: InputOutputLayout.InputOutputLayout designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx:38
- FunctionTooLong: AssertionItem.AssertionItemComponent designer/client/src/components/graph/node-modal/node/NodeContent/TestingContentElements/AssertionItem.tsx:72
- FunctionTooLong: RedeployButton.RedeployButton designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:33
- FunctionTooLong: styles.aceEditorStyles designer/client/src/containers/theme/styles.ts:6
- FunctionTooLong: filtersPart.FiltersPart designer/submodules/packages/components/src/scenarios/filters/filtersPart.tsx:20
- FunctionTooLong: use-touch-sensor.useTouchSensor designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:278
- No assertions: resolves deep values designer/client/src/components/graph/node-modal/typeHelpers.test.ts:17
- No assertions: blocks invalid paths designer/client/src/components/graph/node-modal/typeHelpers.test.ts:43
- No assertions: resolves deep values designer/client/src/components/graph/node-modal/typeHelpers.test.ts:51
- No assertions: blocks invalid paths designer/client/src/components/graph/node-modal/typeHelpers.test.ts:58
- No assertions: should omit brackets designer/client/src/components/graph/node-modal/typeHelpers.test.ts:69
- No assertions: basic components - variable designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:18
- No assertions: basic components - recordVariable designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:31
- No assertions: basic components - filter designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:44
- No assertions: basic components - choice designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:57
- No assertions: basic components - split designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:69
- No assertions: basic components - foreach designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:75
- No assertions: basic components - union designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:82
- No assertions: aggregates - Single Side Join designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:93
- No assertions: aggregates - Full Outer Join designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:103
- No assertions: fragments - Properties designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:111
- No assertions: fragments - Inputs designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:120
- No assertions: fragments - Outputs designer/client/cypress/e2e/autoScreenshotChangeDocs.cy.ts:135
- No assertions: should allow filtering by processing mode designer/client/cypress/e2e/components.cy.ts:257
- No assertions: should display and expand advanced deploy section designer/client/cypress/e2e/deployAdvancedSection.cy.ts:17
- No assertions: should allow drag node designer/client/cypress/e2e/process.cy.ts:157
- No assertions: should make a deploy of the new version designer/client/cypress/e2e/process.cy.ts:200
- No assertions: should allow pan view designer/client/cypress/e2e/processSelection.cy.ts:30
- No assertions: should select only fully covered (to right) designer/client/cypress/e2e/processSelection.cy.ts:41
- No assertions: should select partially covered (to left) designer/client/cypress/e2e/processSelection.cy.ts:50
- No assertions: should switch modes, append and inverse select with shift designer/client/cypress/e2e/processSelection.cy.ts:59
- Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:39
- Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:41
- Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:43
- Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:45
- Unfinished stub — body is `???` designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:47
- Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:47
- Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:82
- Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:102
- Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:123
- Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/CollectionTypesService.scala:10
- Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/DatesTypesService.scala:14
- Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/SimpleTypesService.scala:14
- Unfinished stub — body is `???` engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/HidingVariablesTransformer.scala:32
- Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:39
- Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:41
- Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:43
- Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:45
- Unfinished stub — body is ??? / NotImplementedError designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:47
- Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:47
- Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:82
- Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:102
- Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:123
- Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/CollectionTypesService.scala:10
- Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/DatesTypesService.scala:14
- Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/SimpleTypesService.scala:14
- Unfinished stub — body is ??? / NotImplementedError engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/HidingVariablesTransformer.scala:32
- Swallowed exception (empty catch) designer/client/src/windowManager/LoadingButton.tsx:19
- Swallowed exception (empty catch) designer/client/src/store/draftListener.ts:101
- Swallowed exception (empty catch) designer/client/src/store/draftListener.ts:129
- Swallowed exception (empty catch) designer/client/src/store/draftListener.ts:179
- Swallowed exception (empty catch) REDACTED:38
- Swallowed exception (empty catch) designer/client/src/components/modals/TestingDataRecords/parseRecords.ts:34
- Swallowed exception (empty catch) designer/client/src/components/modals/TestingDataRecords/parseRecords.ts:55
- Swallowed exception (empty catch) designer/client/src/components/graph/SelectionContextProvider.tsx:72
- Swallowed exception (empty catch) designer/client/src/components/graph/SelectionContextProvider.tsx:96
- Swallowed exception (empty catch) designer/client/src/components/graph/node-modal/Variable.tsx:145
- Swallowed exception (empty catch) designer/client/src/components/graph/node-modal/io/RawDisplay.tsx:83
- <TextField> field component without a label designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:175
- <TextField> field component without a label designer/client/src/components/conditionBuilder/ConditionRow.tsx:128
- <TextField> field component without a label designer/client/src/components/dataMapper/DataMapper.tsx:165
- <TextField> field component without a label designer/client/src/components/dataMapper/FieldRow.tsx:299
- <TextField> field component without a label designer/client/src/components/dataMapper/FieldRow.tsx:381
- <TextField> field component without a label designer/client/src/components/dataMapper/SampleJsonPanel.tsx:53
- <TextField> field component without a label designer/client/src/components/modals/TestingDataRecords/AppendFromLiveDataButton.tsx:52
- <TextField> field component without a label designer/client/src/components/modals/TestingDataRecords/PasteRecordsDialog.tsx:96
- <TextField> field component without a label designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:162
- <TextField> field component without a label designer/client/src/containers/settings/SearchField.tsx:31
- FileTooLong: description/NodesApiEndpoints.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/NodesApiEndpoints.scala
- FileTooLong: HttpService/HttpService.ts designer/client/src/http/HttpService/HttpService.ts
- FileTooLong: activities/DbScenarioActivityRepository.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala
- FileTooLong: spel/SpelTyper.scala scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala
- FileTooLong: nodecompilation/NodeCompiler.scala scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/nodecompilation/NodeCompiler.scala
- FileTooLong: periodic/PeriodicProcessService.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala
- FileTooLong: scenarioActivity/Dtos.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/scenarioActivity/Dtos.scala
- FileTooLong: graph/Graph.tsx designer/client/src/components/graph/Graph.tsx
- FileTooLong: api/ScenarioActivityApiHttpService.scala designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ScenarioActivityApiHttpService.scala
- Low cohesion: CaseClassComparator (LCOM4 7) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeComparator.scala:30
- Low cohesion: DbScenarioActivityRepository (LCOM4 5) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:37
- Low cohesion: TableSource (LCOM4 5) engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/io/source/TableSource.scala:47
- Low cohesion: ScenarioActivityApiHttpService (LCOM4 4) designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ScenarioActivityApiHttpService.scala:41
- Low cohesion: DBFetchingProcessRepository (LCOM4 4) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepository.scala:49
- Low cohesion: SlickPeriodicProcessesRepository (LCOM4 4) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/PeriodicProcessesRepository.scala:172
- Low cohesion: JsonSchemaRequestResponseSource (LCOM4 4) engine/lite/components/request-response/src/main/scala/pl/touk/nussknacker/engine/lite/components/requestresponse/jsonschema/sources/JsonSchemaRequestResponseSource.scala:29
- Low cohesion: NodeCompiler (LCOM4 4) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/nodecompilation/NodeCompiler.scala:202
- Change coupling: GenericSourceWithCustomTestingSupport.scala ↔ SampleNodes.scala engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/source/GenericSourceWithCustomTestingSupport.scala:1
- Change coupling: nodeDetails.ts ↔ nodeDetailsState.ts designer/client/src/actions/nk/nodeDetails.ts:1
- Change coupling: TableSource.scala ↔ RowConversions.scala engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/io/source/TableSource.scala:1
- Change coupling: process.ts ↔ reducer.ts designer/client/src/actions/nk/process.ts:1
- Change coupling: EventGeneratorSourceFactory.scala ↔ GenericSourceWithCustomTestingSupport.scala engine/flink/components/base-unbounded/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/EventGeneratorSourceFactory.scala:1
- Change coupling: TableSink.scala ↔ RowConversions.scala engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/io/sink/TableSink.scala:1
- Change coupling: actionTypes.ts ↔ node.ts designer/client/src/actions/actionTypes.ts:1
- Recursive walk over a caller-supplied document has no depth cap utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/util/json/JsonSchemaUtils.scala:19
- Recursive walk over a caller-supplied document has no depth cap designer/client/src/components/graph/node-modal/editors/expression/useAceDndTarget.tsx:22
- Recursive walk over a caller-supplied document has no depth cap designer/client/src/components/dataMapper/dataMapperUtils.ts:331
- Recursive walk over a caller-supplied document has no depth cap designer/client/src/components/builderComponents/typeUtils.ts:6
- Recursive walk over a caller-supplied document has no depth cap designer/client/src/components/builderComponents/typeUtils.ts:16
- Recursive walk over a caller-supplied document has no depth cap designer/client/src/components/builderComponents/typeUtils.ts:40
- Recursive walk over a caller-supplied document has no depth cap components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/decoders/FromJsonSimpleDecoder.scala:15
- TooManyMethods: HttpService designer/client/src/http/HttpService/HttpService.ts:74
- TooManyMethods: Graph designer/client/src/components/graph/Graph.tsx:126
- TooManyMethods: DbScenarioActivityRepository designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:37
- TooManyMethods: GraphBuilder scenario-api/src/main/scala/pl/touk/nussknacker/engine/build/GraphBuilder.scala:16
- TooManyMethods: NodeUtils designer/client/src/components/graph/NodeUtils.ts:14
- TooManyMethods: PeriodicProcessService designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:34
- Duplicated block (5 lines × 2) designer/server/src/main/scala/db/migration/InvalidateComponentsUsagesCache.scala:20
- Duplicated block (5 lines × 2) extensions-api/src/main/scala/pl/touk/nussknacker/engine/migration/ExpressionsMigration.scala:23
- Duplicated block (5 lines × 2) utils/default-helpers/src/main/scala/pl/touk/nussknacker/engine/util/functions/collection.scala:527
- Duplicated block (5 lines × 2) engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:69
- Duplicated block (5 lines × 2) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/SpelReflectionHelper.java:58
- <Select> field component without a label designer/client/src/components/common/DropdownButton.tsx:58
- <Select> field component without a label designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:237
- <Select> field component without a label designer/client/src/components/conditionBuilder/ConditionRow.tsx:111
- <Select> field component without a label designer/client/src/components/dataMapper/FieldRow.tsx:328
- Untrusted text written into markup unescaped REDACTED:53
- Untrusted text written into markup unescaped designer/client/src/components/graph/GlobalCursor.ts:10
- Untrusted text written into markup unescaped designer/client/src/components/graph/node-modal/editors/expression/LineClamp.tsx:106
- Untrusted text written into markup unescaped designer/client/src/components/graph/svg-export/prepareSvg.ts:17
- Swallowed exception (caught, then discarded) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassSerializer.scala:69
- Swallowed exception (caught, then discarded) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:340
- Swallowed exception (caught, then discarded) designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:454
- Swallowed exception (caught, then discarded) designer/client/src/components/modals/saveScenario/useSaveScenario.ts:79
- <Autocomplete> field component without a label designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx:107
- <Autocomplete> field component without a label designer/client/src/components/graph/node-modal/editors/expression/MultiSelectFixedValuesEditor.tsx:86
- <Autocomplete> field component without a label designer/client/src/components/sidePanels/SearchLabeledAutocomplete.tsx:15
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:561
- Duplicated block (10 lines × 2) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeInfo.scala:118
- Duplicated block (10 lines × 2) utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:138
- Duplicated block (23 lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionRow.tsx:86
- Duplicated block (23 lines × 2 locations) designer/client/src/components/graph/node-modal/FragmentOutputDefinition.tsx:25
- Duplicated block (23 lines × 2 locations) designer/client/src/components/modals/GenerateDataAndTestDialog.tsx:38
- Duplicated block (18 lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:65
- Duplicated block (18 lines × 2 locations) designer/client/src/components/dataMapper/dataMapperUtils.ts:215
- Duplicated block (18 lines × 2 locations) designer/submodules/packages/components/src/components/usages/usagesTable.tsx:206
- Dead file (~89 LoC) designer/client/src/components/MenuBar/breadcrumbs.tsx
- Dead file (~89 LoC) designer/client/src/components/aiAssistant/debug/MockAssitantFetch.ts
- Dead file (~89 LoC) designer/client/src/components/modals/PropertiesDialog.tsx
- Weak hash algorithm engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:169
- Weak hash algorithm engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/JarEntryWriter.scala:214
- Weak hash algorithm engine/flink/aws-managed-flink-deployment-manager/src/main/scala/pl/touk/nussknacker/engine/assembly/UberJarAssembler.scala:40
- <RadioGroup> field component without a label designer/client/src/components/graph/node-modal/editors/expression/FixedValuesRadioEditor.tsx:22
- <RadioGroup> field component without a label designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/fields/FixedValuesGroup.tsx:24
- REDACTED
- REDACTED
- MethodTooLong: FlinkProcessRegistrar.createInterpreter engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala:94
- MethodTooLong: FlinkProcessRegistrar.register engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala:103
- ClassTooLong: HttpService designer/client/src/http/HttpService/HttpService.ts:74
- ClassTooLong: ScenarioActivityApiHttpService designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ScenarioActivityApiHttpService.scala:41
- REDACTED
- REDACTED
- Duplicated block (14 lines × 2) components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:86
- Duplicated block (14 lines × 2) engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:50
- Duplicated block (9 lines × 2) components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:86
- Duplicated block (9 lines × 2) engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/typing/RowConversions.scala:81
- Duplicated block (7 lines × 2) defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/UnionParametersMigration.scala:22
- Duplicated block (7 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:117
- Skeleton type — most members are unfinished designer/server/src/main/scala/pl/touk/nussknacker/ui/db/migration/AlwaysUsingSameConnectionDataSource.scala:9
- Skeleton type — most members are unfinished engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/global/ExampleFunctions.scala:25
- Sync-over-async blocking engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MeetingService.scala:17
- Sync-over-async blocking engine/flink/management/src/main/scala/pl/touk/nussknacker/engine/management/rest/HttpFlinkClient.scala:126
- Duplicated block (30 lines × 2 locations) designer/client/src/components/graph/node-modal/DescriptionField.tsx:10
- Duplicated block (30 lines × 2 locations) designer/client/src/components/modals/DeployProcessDialog.tsx:46
- Duplicated block (25 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateTimeEditor.tsx:16
- Duplicated block (25 lines × 2 locations) designer/client/src/components/modals/AddCommentDialog.tsx:28
- Duplicated block (22 lines × 2 locations) designer/client/src/components/dataMapper/dataMapperUtils.ts:339
- Duplicated block (22 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62
- Dead file (~151 LoC) designer/client/src/components/MenuBar/menu.tsx
- Dead file (~151 LoC) designer/client/src/containers/liveData/LiveDataThroughputs.tsx
- Dead file (~139 LoC) designer/client/src/components/aiAssistant/InitializeChatStream.ts
- Dead file (~139 LoC) designer/client/src/containers/ScenarioDescription.tsx
- Dead file (~113 LoC) designer/client/src/components/sidePanels/SidePanelsContext.tsx
- Dead file (~113 LoC) designer/client/src/containers/NodeCreationHandler.tsx
- Dead file (~104 LoC) designer/client/src/components/modals/DeployWithParameters/DeployWithParametersDialog.tsx
- Dead file (~104 LoC) designer/client/src/components/versionInfo.tsx
- Dead file (~80 LoC) designer/client/src/components/tips/Warnings.tsx
- Dead file (~80 LoC) designer/client/src/containers/assertions/addAssertionResultToNodes.tsx
- <Textarea> field component without a label designer/client/src/components/graph/node-modal/editors/expression/TextareaEditor.tsx:36
- <TextArea> field component without a label designer/client/src/components/graph/node-modal/editors/field/Textarea.tsx:32
- Accessibility enforcement below the top rung
- SpelTyper.typeNode (cyclomatic 143) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala:169
- CompareVersionsDialog.VersionsForm (cyclomatic 62) designer/client/src/components/modals/CompareVersionsDialog.tsx:159
- FromJsonTypingResultBasedDecoder.decodeValue (cyclomatic 55) components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/decoders/FromJsonTypingResultBasedDecoder.scala:51
- reducer.graphReducer (cyclomatic 44) designer/client/src/reducers/graph/reducer.ts:170
- DbScenarioActivityRepository.fromEntity (cyclomatic 43) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:720
- FieldRow.FieldRow (cyclomatic 43) designer/client/src/components/dataMapper/FieldRow.tsx:90
- InterpreterInternal.interpretNode (cyclomatic 42) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala:81
- ContextTreeNode.ContextTreeNode (cyclomatic 41) designer/client/src/components/builderComponents/ContextTreeNode.tsx:50
- SpelExpressionSuggester.expressionSuggestionsAux (cyclomatic 39) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala:114
- Table.Table (cyclomatic 39) designer/client/src/components/modals/TestingDataRecords/Table.tsx:56
- ScenarioLabels.ScenarioLabels (cyclomatic 37) designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:132
- DataMapper.DataMapper (cyclomatic 32) designer/client/src/components/dataMapper/DataMapper.tsx:68
- FieldSwitch.FieldSwitch (cyclomatic 31) designer/client/src/components/graph/node-modal/editors/field/FieldSwitch.tsx:72
- DictKeyParameterAdapter.adaptDictKeyExpressionToAvailableEditors (cyclomatic 27) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/dict/DictKeyParameterAdapter.scala:64
- ButtonRoot.ButtonRoot (cyclomatic 27) designer/client/src/components/toolbarComponents/toolbarButtons/ButtonRoot.tsx:12
- NodeSwitcherUtils.adjustEdges (cyclomatic 27) REDACTED:50
- useDataMapper.useDataMapper.defaultFetchTopicDefinitions (cyclomatic 26) designer/client/src/components/dataMapper/useDataMapper.ts:438
- ConditionBuilder.ConditionBuilder (cyclomatic 26) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:47
- drawText.buildFragmentsForTokens::wrapAndPushWords (cyclomatic 26) designer/client/src/components/modals/TestingDataRecords/drawText.ts:141
- FlinkProcessRegistrar.register (cyclomatic 25) engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala:103
- Variable.Variable (cyclomatic 25) designer/client/src/components/graph/node-modal/Variable.tsx:82
- SelectionContextProvider.SelectionContextProvider (cyclomatic 24) designer/client/src/components/graph/SelectionContextProvider.tsx:137
- PrettyValidationErrors.mapIdErrorToNodeError (cyclomatic 23) designer/restmodel/src/main/scala/pl/touk/nussknacker/restmodel/validation/PrettyValidationErrors.scala:425
- FromJsonSchemaBasedDecoder.decode (cyclomatic 23) utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/swagger/decode/FromJsonSchemaBasedDecoder.scala:23
- ToolbarWrapper.ToolbarWrapper (cyclomatic 23) designer/client/src/components/toolbarComponents/toolbarWrapper/ToolbarWrapper.tsx:33
- ExpressionCompiler.compileNodeParameters (cyclomatic 22) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/ExpressionCompiler.scala:175
- useDataMapper.useDataMapper.enrichedContext (cyclomatic 22) designer/client/src/components/dataMapper/useDataMapper.ts:197
- TableEditor.Table (cyclomatic 22) designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:119
- DeployButton.DeployButton (cyclomatic 22) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:33
- RedeployButton.RedeployButton (cyclomatic 22) designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:33
- AssignabilityDeterminer.isSingleTypeMatchesTargetObjType (cyclomatic 21) components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala:151
- reducer.reducer (cyclomatic 21) designer/client/src/components/graph/node-modal/editors/expression/Table/state/reducer.ts:6
- LiveDataThroughputs.LiveDataThroughputs (cyclomatic 21) designer/client/src/containers/liveData/LiveDataThroughputs.tsx:16
- JsonTemplateFromJsonSchemaDeterminer.defaultValueBasedOnSchema (cyclomatic 20) utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonTemplateFromJsonSchemaDeterminer.scala:39
- Selection.getValueRef (cyclomatic 20) scenario-compiler/src/main/java/org/springframework/expression/spel/ast/Selection.java:86
- collapsibleSwitchList.CollapsibleSwitchList (cyclomatic 20) designer/client/src/containers/settings/collapsibleSwitchList.tsx:66
- use-mouse-sensor.useMouseSensor (cyclomatic 20) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:211
- NumberUtils.convertNumberToTargetClass (cyclomatic 19) utils/utils/src/main/java/org/springframework/util/NumberUtils.java:87
- SpelExpressionBuilder.SpelExpressionBuilder (cyclomatic 19) designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:83
- extendActivitiesWithUIData.extendActivitiesWithUIData (cyclomatic 19) designer/client/src/components/toolbars/activities/helpers/extendActivitiesWithUIData.ts:37
- ProcessUtils._findVariablesDefinedInProcess (cyclomatic 19) designer/client/src/common/ProcessUtils.ts:143
- NuSpelExpressionParser.skipToCorrectEndSuffix (cyclomatic 18) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/parser/NuSpelExpressionParser.java:190
- CustomCompleterAceEditor.CustomCompleterAceEditor (cyclomatic 18) designer/client/src/components/graph/node-modal/editors/expression/CustomCompleterAceEditor.tsx:49
- useDataMapper.useDataMapper (cyclomatic 18) designer/client/src/components/dataMapper/useDataMapper.ts:139
- useDataMapper.useDataMapper.handleAutoMap (cyclomatic 18) designer/client/src/components/dataMapper/useDataMapper.ts:328
- ToolbarsContainer.ToolbarsContainer (cyclomatic 18) designer/client/src/components/toolbarComponents/ToolbarsContainer.tsx:133
- drawText.buildFragmentsForTokens (cyclomatic 18) designer/client/src/components/modals/TestingDataRecords/drawText.ts:120
- InputOutputLayout.InputOutputLayout (cyclomatic 18) designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx:38
- NameValueListEditor.NameValueListEditor (cyclomatic 18) designer/client/src/components/graph/node-modal/editors/expression/NameValueList/NameValueListEditor.tsx:43
- DeploymentService.runDeploymentOrRedeploy (cyclomatic 17) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/DeploymentService.scala:97
- spelUtils.parseConditionAst (cyclomatic 17) designer/client/src/components/conditionBuilder/spelUtils.ts:64
- EdgeFields.EdgeFields (cyclomatic 17) designer/client/src/components/graph/node-modal/EdgeFields.tsx:39
- EdgesDndComponent.EdgesDndComponent (cyclomatic 17) designer/client/src/components/graph/node-modal/EdgesDndComponent.tsx:59
- typeUtils.typingResultToSample (cyclomatic 16) designer/client/src/components/builderComponents/typeUtils.ts:12
- Variable.refClazzToValue (cyclomatic 16) designer/client/src/components/graph/node-modal/Variable.tsx:42
- ActivityItemHeader.HeaderActivity (cyclomatic 16) designer/client/src/components/toolbars/activities/ActivityPanelRowItem/ActivityItemHeader.tsx:58
- useActivitiesSearch.useActivitiesSearch.handleGetResults (cyclomatic 16) designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:107
- drawText.tokenizeDataRecords::walk (cyclomatic 16) designer/client/src/components/modals/TestingDataRecords/drawText.ts:70
- NodeCreationHandler.useNodeCreationHandler (cyclomatic 16) designer/client/src/containers/NodeCreationHandler.tsx:14
- usagesTable.UsagesTable (cyclomatic 16) designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34
- Hotspot: designer/client/src/components/modals/CompareVersionsDialog.tsx designer/client/src/components/modals/CompareVersionsDialog.tsx:159
- TodoComment repeated across 14 files utils/flink-components-testkit/src/main/scala/pl/touk/nussknacker/engine/flink/util/test/TestResultSinkFactory.scala:56
- HackComment designer/server/src/main/scala/pl/touk/nussknacker/ui/server/NussknackerHttpServer.scala:108
- SpelTyper.typeNode (cognitive 146) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelTyper.scala:169
- SpelExpressionSuggester.expressionSuggestionsAux (cognitive 107) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSuggester.scala:114
- drawText.buildFragmentsForTokens::wrapAndPushWords (cognitive 75) designer/client/src/components/modals/TestingDataRecords/drawText.ts:141
- DbScenarioActivityRepository.fromEntity (cognitive 62) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:720
- K8sDeploymentManager.runDeployment (cognitive 56) engine/lite/k8sDeploymentManager/src/main/scala/pl/touk/nussknacker/k8s/manager/K8sDeploymentManager.scala:157
- DomainServices.create (cognitive 55) designer/server/src/main/scala/pl/touk/nussknacker/ui/factory/DomainServices.scala:101
- NussknackerAppFactory.createApp (cognitive 55) designer/server/src/main/scala/pl/touk/nussknacker/ui/factory/NussknackerAppFactory.scala:20
- CompareVersionsDialog.VersionsForm (cognitive 51) designer/client/src/components/modals/CompareVersionsDialog.tsx:159
- FromJsonTypingResultBasedDecoder.decodeValue (cognitive 47) components-api/src/main/scala/pl/touk/nussknacker/engine/api/json/decoders/FromJsonTypingResultBasedDecoder.scala:51
- ContextTreeNode.ContextTreeNode (cognitive 46) designer/client/src/components/builderComponents/ContextTreeNode.tsx:50
- ScenarioLabels.ScenarioLabels (cognitive 46) designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx:132
- FieldRow.FieldRow (cognitive 40) designer/client/src/components/dataMapper/FieldRow.tsx:90
- drawText.buildFragmentsForTokens (cognitive 40) designer/client/src/components/modals/TestingDataRecords/drawText.ts:120
- NodeSwitcherUtils.adjustEdges (cognitive 39) REDACTED:50
- Table.Table (cognitive 39) designer/client/src/components/modals/TestingDataRecords/Table.tsx:56
- Selection.getValueRef (cognitive 38) scenario-compiler/src/main/java/org/springframework/expression/spel/ast/Selection.java:86
- Migration.migrate (cognitive 36) designer/server/src/main/scala/db/migration/V1_058__UpdateAndAddMissingScenarioActivitiesDefinition.scala:36
- MigrationService.migrateCurrentScenarioDescription (cognitive 36) designer/server/src/main/scala/pl/touk/nussknacker/ui/migrations/MigrationService.scala:80
- NuRuntimeApp.createProgram (cognitive 36) engine/lite/runtime-app/src/main/scala/pl/touk/nussknacker/engine/lite/app/NuRuntimeApp.scala:46
- CaseClassTypeInfo.getFlatFields (cognitive 35) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeInfo.scala:76
- ButtonRoot.ButtonRoot (cognitive 33) designer/client/src/components/toolbarComponents/toolbarButtons/ButtonRoot.tsx:12
- InterpreterInternal.interpretNode (cognitive 29) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/Interpreter.scala:81
- Variable.Variable (cognitive 29) designer/client/src/components/graph/node-modal/Variable.tsx:82
- FieldSwitch.FieldSwitch (cognitive 28) designer/client/src/components/graph/node-modal/editors/field/FieldSwitch.tsx:72
- ReloadableProcessingTypeDataProvider.reloadAll (cognitive 27) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/processingtype/provider/ReloadableProcessingTypeDataProvider.scala:27
- ConditionBuilder.ConditionBuilder (cognitive 27) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:47
- useActivitiesSearch.useActivitiesSearch.handleGetResults (cognitive 27) designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:107
- reducer.graphReducer (cognitive 27) designer/client/src/reducers/graph/reducer.ts:170
- NumberUtils.convertNumberToTargetClass (cognitive 26) utils/utils/src/main/java/org/springframework/util/NumberUtils.java:87
- DataMapper.DataMapper (cognitive 26) designer/client/src/components/dataMapper/DataMapper.tsx:68
- TableEditor.Table (cognitive 26) designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:119
- DeploymentService.runDeployment (cognitive 25) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/newdeployment/DeploymentService.scala:80
- SpelExpressionBuilder.resolveSpelPath (cognitive 25) designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:47
- DeploymentService.runDeploymentOrRedeploy (cognitive 24) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/DeploymentService.scala:97
- DistributedLeadership.stop (cognitive 23) designer/server/src/main/scala/pl/touk/nussknacker/ui/ha/Leadership.scala:208
- FlinkProcessRegistrar.register (cognitive 23) engine/flink/executor/src/main/scala/pl/touk/nussknacker/engine/process/registrar/FlinkProcessRegistrar.scala:103
- K8sDeploymentManager.cancelScenario (cognitive 23) engine/lite/k8sDeploymentManager/src/main/scala/pl/touk/nussknacker/k8s/manager/K8sDeploymentManager.scala:293
- collapsibleSwitchList.CollapsibleSwitchList (cognitive 22) designer/client/src/containers/settings/collapsibleSwitchList.tsx:66
- alignCells.alignCells (cognitive 22) designer/client/src/components/graph/alignCells.tsx:16
- AssignabilityDeterminer.isSingleTypeMatchesTargetObjType (cognitive 21) components-api/src/main/scala/pl/touk/nussknacker/engine/api/typed/AssignabilityDeterminer.scala:151
- QuestDbFEStatisticsRepository.createRepositoryResource (cognitive 21) designer/server/src/main/scala/pl/touk/nussknacker/ui/db/timeseries/questdb/QuestDbFEStatisticsRepository.scala:179
- PeriodicProcessService.deploy (cognitive 21) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/periodic/PeriodicProcessService.scala:438
- NkGlobalParametersToMapEncoder.decode (cognitive 21) engine/flink/components-api/src/main/scala/pl/touk/nussknacker/engine/flink/api/NkGlobalParameters.scala:97
- Projection.getValueRef (cognitive 21) scenario-compiler/src/main/java/org/springframework/expression/spel/ast/Projection.java:62
- SelectionContextProvider.SelectionContextProvider (cognitive 21) designer/client/src/components/graph/SelectionContextProvider.tsx:137
- ParametersUtils.migrateKafkaParams (cognitive 21) designer/client/src/components/graph/node-modal/ParametersUtils.ts:137
- AceEditorJsonBasedSnippets.getEditorContext (cognitive 21) designer/client/src/components/graph/node-modal/editors/expression/AceEditorJsonBasedSnippets.ts:77
- useDataMapper.useDataMapper (cognitive 21) designer/client/src/components/dataMapper/useDataMapper.ts:139
- extendActivitiesWithUIData.extendActivitiesWithUIData (cognitive 21) designer/client/src/components/toolbars/activities/helpers/extendActivitiesWithUIData.ts:37
- UIProcessValidator.resolveNodeNamesForResult (cognitive 20) designer/server/src/main/scala/pl/touk/nussknacker/ui/validation/UIProcessValidator.scala:240
- Ops.waitForJobState (cognitive 20) engine/flink/minicluster/src/main/scala/pl/touk/nussknacker/engine/flink/minicluster/MiniClusterJobStatusCheckingOps.scala:104
- NumberUtils.parseNumber (cognitive 20) utils/utils/src/main/java/org/springframework/util/NumberUtils.java:210
- use-register-tracking-events.useRegisterTrackingEvents (cognitive 20) designer/client/src/containers/event-tracking/use-register-tracking-events.ts:136
- ParametersUtils.flattenSpelRecord (cognitive 20) designer/client/src/components/graph/node-modal/ParametersUtils.ts:60
- useDataMapper.useDataMapper.validateExpression (cognitive 20) designer/client/src/components/dataMapper/useDataMapper.ts:289
- useDataMapper.useDataMapper.defaultFetchTopicDefinitions (cognitive 20) designer/client/src/components/dataMapper/useDataMapper.ts:438
- ProcessUtils._findVariablesDefinedInProcess (cognitive 20) designer/client/src/common/ProcessUtils.ts:143
- ExpressionCompiler.compileNodeParameters (cognitive 19) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/ExpressionCompiler.scala:175
- DictKeyParameterAdapter.adaptDictKeyExpressionToAvailableEditors (cognitive 19) scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/dict/DictKeyParameterAdapter.scala:64
- reducer.reducer (cognitive 19) designer/client/src/components/graph/node-modal/editors/expression/Table/state/reducer.ts:6
- drawText.tokenizeDataRecords::walk (cognitive 19) designer/client/src/components/modals/TestingDataRecords/drawText.ts:70
- DeploymentsStatusesSynchronizer.synchronizeAll (cognitive 18) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/newdeployment/synchronize/DeploymentsStatusesSynchronizer.scala:22
- CaseClassTypeInfo.getTypeAt (cognitive 18) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/caseclass/CaseClassTypeInfo.scala:167
- NuSpelExpressionParser.skipToCorrectEndSuffix (cognitive 18) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/parser/NuSpelExpressionParser.java:190
- ToolbarWrapper.ToolbarWrapper (cognitive 18) designer/client/src/components/toolbarComponents/toolbarWrapper/ToolbarWrapper.tsx:33
- spelUtils.parseConditionAst (cognitive 18) designer/client/src/components/conditionBuilder/spelUtils.ts:64
- DeployButton.DeployButton (cognitive 18) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:33
- RedeployButton.RedeployButton (cognitive 18) designer/client/src/components/toolbars/scenarioActions/buttons/RedeployButton.tsx:33
- AddProcessDialog.AddProcessDialog (cognitive 18) designer/client/src/components/AddProcessDialog.tsx:25
- LiveDataThroughputs.LiveDataThroughputs (cognitive 18) designer/client/src/containers/liveData/LiveDataThroughputs.tsx:16
- DbScenarioActivityRepository.doModifyActivity (cognitive 17) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/activities/DbScenarioActivityRepository.scala:388
- JsonTemplateFromJsonSchemaDeterminer.defaultValueBasedOnSchema (cognitive 17) utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/JsonTemplateFromJsonSchemaDeterminer.scala:39
- CustomCompleterAceEditor.CustomCompleterAceEditor (cognitive 17) designer/client/src/components/graph/node-modal/editors/expression/CustomCompleterAceEditor.tsx:49
- useDataMapper.useDataMapper.enrichedContext (cognitive 17) designer/client/src/components/dataMapper/useDataMapper.ts:197
- SpelExpressionBuilder.SpelExpressionBuilder (cognitive 17) designer/client/src/components/spelExpressionBuilder/SpelExpressionBuilder.tsx:83
- EdgesDndComponent.EdgesDndComponent (cognitive 17) designer/client/src/components/graph/node-modal/EdgesDndComponent.tsx:59
- use-mouse-sensor.useMouseSensor (cognitive 17) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:211
- NameValueListEditor.NameValueListEditor (cognitive 17) designer/client/src/components/graph/node-modal/editors/expression/NameValueList/NameValueListEditor.tsx:43
- ScenarioStatusProvider.getScenarioStatus (cognitive 16) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/scenariostatus/ScenarioStatusProvider.scala:199
- OptionTypeComparator.compareSerialized (cognitive 16) engine/flink/scala-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/typeinfo/option/OptionTypeComparator.scala:59
- NuSpelExpressionParser.parseExpressions (cognitive 16) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/parser/NuSpelExpressionParser.java:111
- SpelReflectionHelper.convertArguments (cognitive 16) scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/SpelReflectionHelper.java:52
- ButtonMenu.ButtonMenu (cognitive 16) designer/client/src/components/toolbarComponents/toolbarButtons/ButtonMenu.tsx:34
- RawDisplay.useBoundedSelection (cognitive 16) designer/client/src/components/graph/node-modal/io/RawDisplay.tsx:7
- dataMapperUtils.expandDottedKeys (cognitive 16) designer/client/src/components/dataMapper/dataMapperUtils.ts:302
- dataMapperUtils.parseSpelToFields (cognitive 16) designer/client/src/components/dataMapper/dataMapperUtils.ts:378
- useDataMapper.useDataMapper.handleAutoMap (cognitive 16) designer/client/src/components/dataMapper/useDataMapper.ts:328
- EdgeFields.EdgeFields (cognitive 16) designer/client/src/components/graph/node-modal/EdgeFields.tsx:39
- ToolbarsContainer.ToolbarsContainer (cognitive 16) designer/client/src/components/toolbarComponents/ToolbarsContainer.tsx:133
- InputOutputLayout.InputOutputLayout (cognitive 16) designer/client/src/components/graph/node-modal/io/InputOutputLayout.tsx:38
- InitializeChatStream.initializeChatStream (cognitive 16) designer/client/src/components/aiAssistant/InitializeChatStream.ts:74
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (14 corresponding lines) components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:86
- Duplicated block (20 lines × 2) components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:211
- Duplicated block (19 lines × 2) utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/sink/UniversalKafkaSinkFactory.scala:252
- Duplicated block (17–18 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/ScenarioActionRepository.scala:269
- Duplicated block (16 lines × 3) designer/server/src/main/scala/db/migration/V1_058__UpdateAndAddMissingScenarioActivitiesDefinition.scala:111
- Duplicated block (11–16 lines × 2) utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/source/UniversalKafkaSourceFactory.scala:119
- Duplicated block (11–13 lines × 2) engine/flink/components/base/src/main/scala/pl/touk/nussknacker/engine/flink/util/transformer/UnionTransformer.scala:34
- Duplicated block (12 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/api/ManagementResources.scala:175
- Duplicated block (10–12 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:160
- Duplicated block (11–12 lines × 2) engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/transformer/CustomTimestampExtractingTransformationCopy.scala:17
- Duplicated block (8–11 lines × 2) designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:289
- Duplicated block (8–10 lines × 2) defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/DefaultConfigCreator.scala:14
- Duplicated block (6 lines × 3) components-api/src/main/scala/pl/touk/nussknacker/engine/javaapi/context/transformation/JavaDynamicComponent.scala:89
- Duplicated block (5 lines × 3) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepository.scala:79
- Duplicated block (13 lines × 2) designer/server/src/main/scala/db/migration/V1_061__PeriodicDeploymentManagerTablesDefinition.scala:64
- Duplicated block (11 lines × 2) engine/lite/embeddedDeploymentManager/src/main/scala/pl/touk/nussknacker/engine/embedded/EmbeddedRequestResponseScenarioValidator.scala:16
- Duplicated block (6 lines × 2) defaultModel/src/main/scala/pl/touk/nussknacker/defaultmodel/migrations/GroupByMigration.scala:15
- Duplicated block (8 lines × 2) engine/flink/test-utils/src/main/scala/pl/touk/nussknacker/engine/process/helpers/SampleNodes.scala:430
- Unstable project flinkDeploymentManager
- Unstable project flinkExecutor
- Unstable project flinkKafkaComponentsUtils
- Unstable project liteRequestResponseComponents
- Off the main sequence: liveDataCollector
- README may be stale
- Outbound HTTP without resilience designer/client/src/api.ts:7
- Duplication concentrated across 7 sibling directories (19 clone groups) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164
- Duplication concentrated across 6 sibling directories (13 clone groups) designer/client/src/components/toolbars/process/buttons/SaveButton.tsx:58
- Duplication concentrated across 3 sibling directories (10 clone groups) designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34
- Duplication concentrated across 2 sibling directories (7 clone groups) designer/client/configs/simpleScriptPlugin.ts:8
- Duplication concentrated across 5 sibling directories (6 clone groups) designer/client/src/components/graph/node-modal/editors/expression/FixedValuesEditor_ReactSelectCreatableVariant.tsx:62
- Duplicated block with local edits (111 matched lines × 2 locations) designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:113
- Duplicated block (109 lines × 2 locations) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:83
- Duplicated block with local edits (105 matched lines × 2 locations) designer/client/src/components/conditionBuilder/ConditionBuilder.tsx:164
- Duplicated block with local edits (75 matched lines × 2 locations) designer/submodules/packages/components/src/components/usages/usagesTable.tsx:34
- Duplicated block with local edits (50 matched lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/Duration/DurationEditor.tsx:32
- Duplicated block (50 lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueWithSuggestionVariant.tsx:16
- Duplicated block (49 lines × 2 locations) designer/client/configs/simpleScriptPlugin.ts:8
- Duplicated block (48 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:63
- Duplicated block (47 lines × 2 locations) designer/client/src/http/HttpService/HttpService.ts:263
- Duplicated block (46 lines × 2 locations) designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:25
- Duplicated block (41 lines × 2 locations) designer/client/src/components/notifications/copyTooltip.tsx:15
- Duplicated block with local edits (38 matched lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/StringBooleanVariants/AnyValueVariant.tsx:14
- Duplicated block (37 lines × 2 locations) designer/client/src/http/HttpService/HttpService.ts:927
- Duplicated block (34 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:159
- Duplicated block (28 lines × 2 locations) designer/client/src/components/graph/node-modal/fragment-input-definition/settings/variants/DefaultVariant.tsx:35
- Duplicated block (24 lines × 3 locations) designer/client/src/components/graph/node-modal/NodeTypeDetailsContent.tsx:60
- Duplicated block with local edits (22 matched lines × 2 locations) designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx:6
- Duplicated block (21 lines × 2 locations) designer/client/src/components/graph/node-modal/editors/expression/Table/CellMenu.tsx:45
- Duplicated block (20 lines × 2 locations) designer/client/src/common/copyToClipboard/useCopyToClipboard.ts:5
- Duplicated block (19 lines × 2 locations) designer/client/configs/withModuleFederationPlugins.ts:64
- Duplicated block (19 lines × 3 locations) designer/client/src/components/toolbars/scenarioActions/buttons/CancelDeployButton.tsx:78
- Duplicated block (17 lines × 2 locations) designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:99
- Duplicated block (17 lines × 4 locations) designer/client/src/components/graph/node-modal/DescriptionField.tsx:23
- Complex function FieldRow (cyclomatic 40, cognitive 35) designer/client/src/components/dataMapper/FieldRow.tsx:90
- Complex function ContextTreeNode (cyclomatic 36, cognitive 35) designer/client/src/components/builderComponents/ContextTreeNode.tsx:50
- Complex function (anonymous) (cyclomatic 26, cognitive 75) designer/client/src/components/modals/TestingDataRecords/drawText.ts:141
- Complex function (anonymous) (cyclomatic 22, cognitive 24) designer/client/src/components/dataMapper/useDataMapper.ts:197
- Complex function (anonymous) (cyclomatic 19, cognitive 20) designer/client/src/common/ProcessUtils.ts:148
- Complex function DataMapper (cyclomatic 19, cognitive 17) designer/client/src/components/dataMapper/DataMapper.tsx:68
- Complex function ToolbarWrapper (cyclomatic 19, cognitive 16) designer/client/src/components/toolbarComponents/toolbarWrapper/ToolbarWrapper.tsx:33
- Complex function buildFragmentsForTokens (cyclomatic 18, cognitive 43) designer/client/src/components/modals/TestingDataRecords/drawText.ts:120
- Complex function parseConditionAst (cyclomatic 17, cognitive 18) designer/client/src/components/conditionBuilder/spelUtils.ts:64
- Complex function typingResultToSample (cyclomatic 17, cognitive 16) designer/client/src/components/builderComponents/typeUtils.ts:12
- Complex function VariantWrapper (cyclomatic 17, cognitive 16) designer/client/src/components/toolbarComponents/toolbarButtons/ButtonRoot.tsx:12
- Complex function (anonymous) (cyclomatic 16, cognitive 28) designer/client/src/components/toolbars/activities/useActivitiesSearch.ts:107
- Complex function adjustEdges (cyclomatic 16, cognitive 25) REDACTED:50
- Complex function (anonymous) (cyclomatic 16, cognitive 19) designer/client/src/components/modals/TestingDataRecords/drawText.ts:70
- Complex function refClazzToValue (cyclomatic 16, cognitive 14) designer/client/src/components/graph/node-modal/Variable.tsx:42
- designer/client/src/http/HttpService/HttpService.ts: 1226 lines of code designer/client/src/http/HttpService/HttpService.ts:1
- designer/client/src/components/graph/Graph.tsx: 743 lines of code designer/client/src/components/graph/Graph.tsx:1
- designer/client/src/components/dataMapper/useDataMapper.ts: 589 lines of code designer/client/src/components/dataMapper/useDataMapper.ts:1
- designer/client/src/components/modals/CompareVersionsDialog.tsx: 569 lines of code designer/client/src/components/modals/CompareVersionsDialog.tsx:1
- designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx: 530 lines of code designer/client/src/components/graph/node-modal/editors/expression/Table/TableEditor.tsx:1
- designer/client/src/reducers/graph/reducer.ts: 501 lines of code designer/client/src/reducers/graph/reducer.ts:1
- designer/client/src/components/dataMapper/FieldRow.tsx: 467 lines of code designer/client/src/components/dataMapper/FieldRow.tsx:1
- designer/client/src/components/dataMapper/dataMapperUtils.ts: 452 lines of code designer/client/src/components/dataMapper/dataMapperUtils.ts:1
- designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts: 434 lines of code designer/client/src/components/toolbarComponents/sensors/use-touch-sensor.ts:1
- designer/client/src/components/dataMapper/DataMapper.tsx: 417 lines of code designer/client/src/components/dataMapper/DataMapper.tsx:1
- Dependency Freshness
- Dead file (~436 LoC) designer/client/src/components/toolbars/scenarioDetails/ScenarioLabels.tsx
- Dead file (~260 LoC) designer/client/src/components/toolbars/search/utils.ts
- Dead file (~252 LoC) designer/client/src/containers/Visualization.tsx
- Dead file (~197 LoC) designer/client/src/components/toolbarComponents/ToolbarsLayer.tsx
- Dead file (~172 LoC) designer/client/src/components/toolbars/creator/CreatorPanel.tsx
- Dead file (~161 LoC) designer/client/src/windowManager/ContentGetter.tsx
- Dead file (~160 LoC) designer/client/src/components/common/DropdownButton.tsx
- Dead file (~156 LoC) designer/client/src/components/AddProcessDialog.tsx
- Dead file (~140 LoC) designer/client/src/components/toolbars/search/AdvancedSearchFilters.tsx
- Dead file (~137 LoC) designer/client/src/containers/Auth/strategies/OAuth2Strategy.ts
- Dead file (~127 LoC) designer/client/src/components/graph/node-modal/node/DescriptionDialog.tsx
- Dead file (~126 LoC) designer/client/src/components/aiAssistant/components/Composer.tsx
- Dead file (~122 LoC) designer/client/src/components/modals/CalculateCounts/RefreshSelectButton.tsx
- Dead file (~121 LoC) designer/client/src/components/modals/MoreScenarioDetailsDialog.tsx
- Dead file (~117 LoC) designer/client/src/components/modals/DeployWithParameters/AdvancedParameters.tsx
- Dead file (~110 LoC) designer/client/src/components/aiAssistant/ModelAdapter.ts
- Dead file (~109 LoC) designer/client/src/components/aiAssistant/tools/ScenarioDataAIToolkit.tsx
- Dead file (~108 LoC) designer/client/src/containers/liveData/animationHelpers.ts
- Dead file (~105 LoC) designer/client/src/components/toolbars/search/SearchResults.tsx
- Dead file (~102 LoC) designer/client/src/containers/settings/SettingsView.tsx
- Dead file (~93 LoC) designer/client/src/components/modals/CalculateCounts/CalculateCountsDialog.tsx
- Dead file (~91 LoC) designer/client/configs/withModuleFederationPlugins.ts
- Dead file (~90 LoC) designer/client/src/components/aiAssistant/messageHelpers.ts
- Dead file (~87 LoC) designer/client/src/containers/AddComponentsButtons.tsx
- Dead file (~84 LoC) designer/client/src/components/aiAssistant/components/AssistantMessage.tsx
- Dead file (~81 LoC) designer/client/src/components/sidePanels/CollapsiblePanel.tsx
- Unlisted import '@emotion/serialize' designer/client/src/components/graph/EspNode/stickyNote/advancedStickyNoteConfig.ts:1
- Unlisted import '@mui/styled-engine' designer/client/src/components/graph/node-modal/io/PanelButton.tsx:2
- Unlisted import 'assistant-stream' designer/client/src/components/aiAssistant/useCheckPermission.tsx:1
- Unlisted import 'css-box-model' designer/client/src/components/toolbarComponents/sensors/use-mouse-sensor.ts:22
- Unused dependency 'd3-transition'
- Unused dependency 'glob'
- Unused dependency 'moment-duration-format'
- Async function without AbortSignal: read designer/submodules/packages/components/src/settings/i18n.ts:16
Minor — 543 finding(s)
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/ActionService.scala:1
- Orphaned file scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/definition/clazz/ClassDefinitionExtractor.scala:1
- Orphaned file scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/spel/internal/propertyAccessors.scala:1
- Orphaned file utils/math-utils/src/main/scala/pl/touk/nussknacker/engine/util/MathUtils.scala:1
- Orphaned file extensions-api/src/main/scala/pl/touk/nussknacker/engine/api/process/ClassExtractionSettings.scala:1
- Orphaned file utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/encode/JsonSchemaOutputValidator.scala:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/util/PdfExporter.scala:1
- Orphaned file scenario-compiler/src/main/java/pl/touk/nussknacker/engine/spel/parser/NuSpelExpressionParser.java:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/newdeployment/DeploymentService.scala:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/migrations/MigrationService.scala:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/MigrationApiEndpoints.scala:1
- Orphaned file utils/json-utils/src/main/scala/pl/touk/nussknacker/engine/json/swagger/SwaggerTyped.scala:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/StatisticsApiEndpoints.scala:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/api/description/AppApiEndpoints.scala:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/statistics/ScenarioStatistics.scala:1
- Orphaned file components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/NodeDependency.scala:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/reconciliation/ScenarioDeploymentReconciler.scala:1
- Orphaned file scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/nodecompilation/BuiltInNodeCompiler.scala:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/DeploymentService.scala:1
- Orphaned file components-api/src/main/scala/pl/touk/nussknacker/engine/api/definition/ParameterDeclaration.scala:1
- Orphaned file designer/server/src/main/scala/pl/touk/nussknacker/ui/process/deployment/scenariostatus/ScenarioStatusProvider.scala:1
- Orphaned file engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/batch/TableJoinComponent.scala:1
- Orphaned file scenario-compiler/src/main/scala/pl/touk/nussknacker/engine/compile/FragmentResolver.scala:1
- Orphaned file utils/schemed-kafka-components-utils/src/main/scala/pl/touk/nussknacker/engine/schemedkafka/encode/ToAvroSchemaBasedEncoder.scala:1
- Orphaned file utils/utils/src/main/java/org/springframework/util/NumberUtils.java:1
- Duplicated predicate designer/client/src/components/dataMapper/dataMapperUtils.ts:380
- Duplicated predicate designer/submodules/packages/components/src/scenarios/filters/filterRules.tsx:25
- Duplicated predicate designer/client/src/components/dataMapper/dataMapperUtils.ts:353
- Duplicated predicate designer/submodules/packages/components/src/components/useComponentsQuery.tsx:31
- Duplicated predicate designer/client/src/containers/settings/SearchField.tsx:9
- Duplicated predicate designer/client/src/containers/settings/SearchField.tsx:8
- Duplicated predicate designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DateEditor.tsx:50
- Duplicated predicate designer/submodules/packages/components/src/components/useComponentsQuery.tsx:32
- Duplicated predicate designer/client/src/components/ValueDragPreview.tsx:83
- Duplicated predicate designer/client/src/components/ComponentDragPreview.tsx:46
- Duplicated predicate designer/client/src/components/builderComponents/typeUtils.ts:19
- Duplicated predicate designer/client/configs/simpleScriptPlugin.ts:22
- Duplicated predicate designer/client/src/components/graph/node-modal/editors/expression/Cron/CronEditor.tsx:42
- Duplicated predicate designer/client/src/components/graph/node-modal/editors/expression/DateTimeEditor/DatepickerEditor.tsx:80
- Duplicated predicate designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx:116
- Duplicated predicate designer/client/src/components/graph/node-modal/editors/expression/MultiSelectFixedValuesEditor.tsx:98
- Duplicated predicate designer/client/src/reducers/graph/testing.ts:34
- Duplicated predicate designer/client/src/reducers/graph/testing.ts:28
- Duplicated predicate designer/client/src/components/graph/node-modal/editors/expression/DictParameterEditor/DictParameterEditor.tsx:29
- Duplicated predicate designer/client/src/components/dataMapper/dataMapperUtils.ts:394
- Duplicated predicate designer/client/src/components/toolbars/scenarioActions/buttons/DeployButton.tsx:56
- Duplicated predicate designer/client/src/components/builderComponents/ContextTreeNode.tsx:73
- Duplicated predicate designer/client/src/components/CommandBar/ResultFlagItem.tsx:28
- Duplicated predicate engine/flink/components-utils/src/main/scala/pl/touk/nussknacker/engine/flink/api/state/EvictableState.scala:114
- Duplicated predicate engine/flink/components/table/src/main/scala/pl/touk/nussknacker/engine/flink/table/typing/ToTableTypeEncoder.scala:44
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/api/ProcessesResourcesSpec.scala:261
- Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/api/ProcessesResourcesSpec.scala:399
- Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/config/ConfigurationTest.scala:79
- Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/config/ConfigurationTest.scala:119
- Disabled test designer/server/src/test/scala/pl/touk/nussknacker/ui/process/processingtype/ScenarioParametersServiceTest.scala:271
- Disabled test engine/flink/management/src/it/scala/pl/touk/nussknacker/engine/management/streaming/BaseFlinkDeploymentManagerSpec.scala:242
- Disabled test engine/flink/tests/src/test/scala/pl/touk/nussknacker/defaultmodel/StateCompatibilityTest.scala:126
- Disabled test scenario-compiler/src/test/scala/pl/touk/nussknacker/engine/spel/SpelExpressionSpec.scala:2792
- Disabled test security/src/test/scala/pl/touk/nussknacker/ui/security/api/SecurityApiSpec.scala:51
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Off-boarding risk: anonymized user #4
- README/code drift README.md:61
- README/code drift CONTRIBUTING/README.md:58
- README/code drift CONTRIBUTING/README.md:205
- README/code drift designer/client/README.md:37
- Fat interface: ListenerScenarioWithDetails (21 abstract members) designer/listener-api/src/main/scala/pl/touk/nussknacker/ui/listener/ListenerScenarioWithDetails.scala:9
- Fat interface: ProcessService (18 abstract members) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/ProcessService.scala:129
- Fat interface: PeriodicProcessesRepository (20 abstract members) designer/server/src/main/scala/pl/touk/nussknacker/ui/process/repository/PeriodicProcessesRepository.scala:82
- Placeholder literal left in code engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:22
- Placeholder literal left in code engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:46
- Placeholder literal left in code engine/flink/management/dev-model/src/main/scala/pl/touk/nussknacker/engine/management/sample/service/MultiSelectEditorService.scala:62
- Console output used as the logging channel engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-es-bundle-core.js:2
- Console output used as the logging channel engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui-standalone-preset.js:2
- Console output used as the logging channel engine/lite/request-response/runtime/src/main/resources/swagger-ui/swagger-ui.js:1
- Silent fallback default in catch designer/client/src/components/modals/TestingDataRecords/drawText.ts:56
- Silent fallback default in catch designer/client/src/components/modals/TestingDataRecords/utils.ts:44
- Silent fallback default in catch designer/client/src/components/graph/node-modal/editors/expression/MultiSelectFixedValuesEditor.tsx:50
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- No ADRs
- Large public API surface
- Logging is not universal
- Benchmarks don't track allocations benchmarks/src/test/scala/pl/touk/nussknacker/engine/benchmarks/suggester/ExpressionSuggesterBenchmark.scala
- Type-only dependency 'react-notification-system' in production deps designer/client/src/actions/notificationActions.tsx:5
- No security response headers detected examples/installation/nginx/nginx.conf:2
- Not all async functions that make a request accept an AbortSignal
- Interpolated log message defeats structured logging live-data-collector/src/main/scala/pl/touk/nussknacker/engine/livedata/LiveDataUploader.scala:46
- Scala's null is not held to the type system everywhere
Minor — 76 finding(s)
- Outdated: ch.qos.logback:logback-classic
- Outdated: ch.qos.logback:logback-core
- Outdated: com.auth0:jwks-rsa
- Outdated: com.azure:azure-core-http-okhttp
- Outdated: com.azure:azure-data-schemaregistry
- Outdated: com.azure:azure-identity
- Outdated: com.cronutils:cron-utils
- Outdated: com.fasterxml.jackson.core:jackson-annotations
- Outdated: com.fasterxml.jackson.core:jackson-core
- Outdated: com.fasterxml.jackson.core:jackson-databind
- Outdated: com.fasterxml.jackson.dataformat:jackson-dataformat-cbor
- Outdated: com.fasterxml.jackson.dataformat:jackson-dataformat-toml
- Outdated: com.fasterxml.jackson.dataformat:jackson-dataformat-yaml
- Outdated: com.fasterxml.jackson.datatype:jackson-datatype-guava
- Outdated: com.fasterxml.jackson.datatype:jackson-datatype-jdk8
- Outdated: com.fasterxml.jackson.datatype:jackson-datatype-joda
- Outdated: com.fasterxml.jackson.datatype:jackson-datatype-jsr310
- Outdated: com.fasterxml.jackson.module:jackson-module-parameter-names
- Outdated: com.github.ben-manes.caffeine:caffeine
- Outdated: com.github.erosb:everit-json-schema
- Outdated: com.microsoft.azure:azure-schemaregistry-kafka-avro
- Outdated: com.networknt:json-schema-validator
- Outdated: com.typesafe:config
- Outdated: com.typesafe.netty:netty-reactive-streams
- Outdated: com.zaxxer:HikariCP
- Off the main sequence: commonApi
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8364e7cfd771456fbf983bd2fd1a59f9/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8364e7cfd771456fbf983bd2fd1a59f9/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude designer/client/src/brace --exclude designer/client/test/Editors --exclude designer/client/test/Process/FrgamentInputDefinition . | 93 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 150 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude designer/client/src/brace --exclude designer/client/test/Editors --exclude designer/client/test/Process/FrgamentInputDefinition . | 1 | artifacts/raw/semgrep-gdpr.json |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |