flowdrop 1.2.0

[1.2.0] - 2026-03-19

Added

• Dynamic input/output ports: Node types can now declare dynamic ports whose number and names are determined at runtime by configuration. Introduces DynamicPortTrait for node processors, a ReservedName constants class to prevent name collisions, and a new DataMapper node processor that maps input fields to output ports dynamically.
• ExpressionEvaluator plugin system: New #[ExpressionEvaluator] attribute-based plugin manager with four built-in engines — property_path (Symfony PropertyAccess), expression_language (Symfony ExpressionLanguage), twig (Twig), and jsonpath (JSONPath via flowdrop_runtime). Replaces hardcoded service dependencies in expression-heavy processors with a configurable, swappable architecture.
• EventCategory::Integration: New enum case for grouping event types triggered by external platform invocations (e.g. Orchestration Invoke).
• Module installation kernel tests: ModuleInstallationTest now covers all 18 FlowDrop modules via a @dataProvider, simulating drush en <module> for each and catching missing dependency declarations automatically.

Changed

• DataExtractor (v2.1.0): Replaces direct JsonPathService dependency with the ExpressionEvaluator plugin system. Adds a configurable engine parameter (defaults to jsonpath — existing behavior preserved).
• DataShaper (v1.1.0): Replaces DataMapperService with the ExpressionEvaluator plugin system. Adds a configurable engine parameter (defaults to property_path — existing behavior preserved).
• DataMapper (v1.0.0): Switches from hardcoded Twig to a configurable engine parameter (defaults to expression_language).
• Node type config entities for data_extractor, data_shaper, and data_mapper updated with the new engine parameter.
• OrchestrationInvoke event type plugin now uses the typed EventCategory::Integration constant instead of a bare string.

Fixed

• Fixed flowdrop_node_type not declared as an explicit dependency of flowdrop_job, which could cause install failures in a fresh environment.
• Fixed NULL node type values causing errors in pipeline job timeline components.
• Fixed EventCategory enum not converted to string before use in trigger services.
• Fixed dynamic port configurable flag not toggleable by site administrators in the node type form.