Add saving of data extension editor table to YAML#2264
Merged
Conversation
This adds the ability to save the modeled methods in the data extensions editor to a YAML file named after the database name. It will save it to the `ql` submodule for now. Support for data extension packs will be added later.
This was referenced Apr 4, 2023
charisk
approved these changes
Apr 6, 2023
Contributor
charisk
left a comment
There was a problem hiding this comment.
LGTM, just one code readability comment that I'd like to see addressed before merging.
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.
This adds the ability to save the modelled methods in the data extensions editor to a YAML file named after the database name. It will save it to the
qlsubmodule for now. Support for data extension packs will be added later.Based on #2263
Checklist
ready-for-doc-reviewlabel there.