Draft
Conversation
|
Contributor
Author
|
@Matthbo Could you take a look at how this is implemented right now? Because of my inexperience with xml I am uncertain if storing the flowelements like this will cause any issues with Configurations or if they will get ignored because of the flow namespace prefixed to it. It would seem that the xsd is picking up on it and flagging it as wrong (as you can see in the screenshot in the title of this PR). I am also wondering if you perhaps had a more elegant solution overall. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.



<flow:FlowElements>element so they can be directly stored within the configuration xml, directly underneath the pipeline: