-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MAINTENANCE] Remove remaining references to block style datasources #9881
[MAINTENANCE] Remove remaining references to block style datasources #9881
Conversation
✅ Deploy Preview for niobium-lead-7998 canceled.
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #9881 +/- ##
===========================================
- Coverage 77.77% 77.36% -0.42%
===========================================
Files 494 493 -1
Lines 42389 42360 -29
===========================================
- Hits 32967 32770 -197
- Misses 9422 9590 +168
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
… fix a test to use ephemeral context)
…ock-style-datasoures
…ock-style-datasoures
This reverts commit fe6be93.
include_pandas: bool = True, | ||
include_spark: bool = True, | ||
) -> AbstractDataContext: | ||
def build_in_memory_runtime_context() -> AbstractDataContext: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not relevant to your PR but I don't know why this method is in our repo if we only really use it as a test util - same comment for a lot of the methods in here we might want to write a ticket about removing them to undo some import cycles they cause
tests/data_context/abstract_data_context/test_list_datasources.py
Outdated
Show resolved
Hide resolved
@@ -598,7 +597,10 @@ def test_escape_all_config_variables_skip_substitution_vars( | |||
|
|||
|
|||
@pytest.mark.filesystem | |||
def test_create_data_context_and_config_vars_in_code(tmp_path_factory, monkeypatch): | |||
# @mock.patch.object(sa, "create_engine") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit - can we remove?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done!
tests/expectations/core/test_expect_queried_column_value_frequency_to_meet_threshold.py
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't gotten too far but wanted to send what I had before more meetings. I've looked through the non-test code and some of the test files.
include_pandas: bool = True, | ||
include_spark: bool = True, | ||
) -> AbstractDataContext: | ||
def build_in_memory_runtime_context() -> AbstractDataContext: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a test util in the normal code package?
Now it's building a context with no datasources, maybe we can delete this whole function? Maybe that involves deleting BaseDatasource
which is happening as a followup?
@@ -894,61 +893,6 @@ def titanic_pandas_data_context_with_v013_datasource_with_checkpoints_v1_with_em | |||
context = get_context(context_root_dir=context_path) | |||
assert context.root_directory == context_path | |||
|
|||
datasource_config: str = f""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering if we can delete this whole fixture since there is no longer a datasource.
Removes all references to block style
Datasource
class. Note: This does not removeBaseDatasource
; that will be removed in a followup PR.NOTE: This raises some new
DataContextErrors
in places if we get a non-fluent datasource. These errors should not be hit and are just to make the type checker happy.There are a lot of other test deletions in here that I think are reasonable. The main categories:
Datasource
testsinvoke lint
(usesruff format
+ruff check
)For more information about contributing, see Contribute.
After you submit your PR, keep the page open and monitor the statuses of the various checks made by our continuous integration process at the bottom of the page. Please fix any issues that come up and reach out on Slack if you need help. Thanks for contributing!