Remove prefix underscore from slugified schema names #91
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
|
Note that the workflow failure here is another test threshold issue. |
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 PR updates our schema name generator so that schemas that start with numbers are not prefixed with an underscore. The prefix underscore is designed to prevent invalid schemas (ones that start with numbers), but it is unnecessary for our use case since all dbt-generated schemas for non-main branches are prefixed with
dev_orci_.Including the underscore prefix in the name generator results in schema names with repeated underscores when the feature branch is generated from an issue, i.e.
ci__70-create-reporting-view-with-most-recent-boundaries_census.