Fix skip_add_data_types condition in update_columns_data_type
#140
Conversation
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
|
Ah good catch, thanks. 🙇 🙏 |
|
@z3z1ma Thank you for merging, and I'm waiting for the new version to be released with the fixes reflected! |
|
I found https://github.com/z3z1ma/dbt-osmosis/releases/tag/v0.12.9, thank you! |
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.
@z3z1ma After updating dbt-osmosis to version 0.12.8, I noticed that the
data_typeattribute disappears from within the yaml. After reading the source code, I noticed that theskip_add_data_typescondition in theupdate_columns_data_typefunction is wrong, so I will fix it.