-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[components] Ensure dg component check uses configured components pat…
…h and other tweaks (#27386) ## Summary & Motivation This makes a few tweaks around the new `dg component check` command and it's tests: - Adds a clause to ensure this is running inside a code location (something we do for all `dg component ...` commands) - Change to use the parametrized component path derived from context instead of a hardcoded components path (which will break if the user tries to configure the components path) - Does a little refactoring around the tests to make them more coherent with the rest of `dagster-dg` tests. In particular: - makes the `create_code_location_from_components` utility build off of `isolated_example_code_location_foo_bar`, which is used everywhere else - nests the `check` tests with the other `dg component ...` tests ## How I Tested These Changes New unit tests.
- Loading branch information
Showing
5 changed files
with
92 additions
and
76 deletions.
There are no files selected for viewing
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
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
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
File renamed without changes.
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