Fix: Raise a DbtMeshifyError if a project path is provided that does not contain a dbt_project.yml file
#163
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
…s missing raises a FatalMesifyException
… a bogus dbt project is provided
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.
Description and Motivation
Previously, it was possible for a user to provide a project path that is not real. For instance, running the command in the wrong directory! In this PR, I've added a check to include that a
dbt_project.ymlfile is present in the project path, and if not, aDbtMeshifyExceptionis raised with a corresponding error message. Along the way, I added tests for each command to confirm that the correct error message is returned if an invalid project path is provided.Resolves: #87
Example