Allow Variable Steps in the Dataflow Processor #509
Conversation
…d step processing
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dataflow-v2 #509 +/- ##
==============================================
Coverage ? 66.13%
==============================================
Files ? 252
Lines ? 7480
Branches ? 1139
==============================================
Hits ? 4947
Misses ? 2271
Partials ? 262 ☔ View full report in Codecov by Sentry. |
|
In combination with #468, this should allow us to better separate the steps from each other, allowing to load arbitrary steps known to the program (with no more requirement that they have to appear in a |
* git, doc: document new optional scope and much more readable regex in commit-msg * feat(commit-msg): print out message even if it is invalid * feat(commit-msg): print commit message even if it is incorrect * doc: refer to the contributin md instead of just printing the regex if the git commit message is wrong * refactor(commit-msg): slightly reformat output * refactor(commit-msg): remove the `log` type * doc(contributing): document new scopes for commit messages
…ataflow-processors
… cleanup decoration toposort
… improve handling
…ems to be a misplaced performance option
This reverts commit 9d919da.
…he string construction if it is not needed
EagleoutIce
deleted the
508-allow-multiple-functions-to-be-used-as-dataflow-processors
branch
|
This pull request is included in v2.0.0 (see Release v2.0.0 (Dataflow v2)). |
4 similar comments
|
This pull request is included in v2.0.0 (see Release v2.0.0 (Dataflow v2)). |
|
This pull request is included in v2.0.0 (see Release v2.0.0 (Dataflow v2)). |
|
This pull request is included in v2.0.0 (see Release v2.0.0 (Dataflow v2)). |
|
This pull request is included in v2.0.0 (see Release v2.0.0 (Dataflow v2)). |
This revises the step system by adding dependencies to the mix, allowing to create pipelines based on a selection of steps. This pipeline is automatically resolved and ordered, and then to be given to the
SteppingSlicer, which is to be renamed according to the pipeline scheme. I am open to suggestions.While the PR provides full compatibility at the moment, i will probably break that (although the stepping slicer facade my live on for
1.x.xto provide compatibility). We should introduce a new milestone for 2.x.x and schedule the removal of said component there.