-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Navigate Pipeline via Pipes instead of Blocks #491
Merged
+236
−215
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
a048395
Replace model-util helper methods with PipelineWrapper
georg-schwarz 7831feb
Add test for pipeline without pipes
georg-schwarz 7be2e28
Rename methods of PipelineWrapper
georg-schwarz dc33dfe
Add license to PipelineWrapper
georg-schwarz 319488b
Remove duplicated starting blocks
georg-schwarz 37f9c1c
Alter GTFS static example to use composite block
georg-schwarz 46ae21d
Rename pipesContainer argument of executeBlocks
georg-schwarz f1f3bee
Rename arguments to pipesContainer in PipelineWrapper
georg-schwarz 91e8987
Rename followPipe methods to getChildBlock and getParentBlock
georg-schwarz 0b71a9d
Move getBlocksInTopologicalSorting function to PipelineWrapper
georg-schwarz 32c87d9
Update use of old followPipe method in interpreter-lib
georg-schwarz cda9e9a
Ensure pipeline wrapper can be created in validations
georg-schwarz a224ee9
Fix bug in pipeline validation
georg-schwarz 815a580
Improve typing of PipelineWrapper
georg-schwarz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is not part of the PR but this seems very boring. We could enhance the
GTFSExtractor
in the std lib to also include picking a file and parsing it as CSV, maybe as a composite block inside a composite block.The new block could be called
GTFSFileExtractor
and take anurl
and apath
as property, then use the existingGTFSExtractor
with the url and theFilePicker
with the file, then parse that file as CSV file. This would reduce this example by 3 blocks and 3 lines for every file (so 33 less blocks and 33 less lines in the pipeline itself!).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you don't mind I'd leave it as it is for now.
But your example looks interesting, also in the face of optimizations. In the best case, we would also reuse executed blocks multiple times. I'm not sure if that would be the case in the current implementation, so I'd leave it open for a follow-up issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I agree on all counts, it's not in the scope of this PR anyway.