feat: restructure codebase with core/ module and explicit imports #21
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
🎯 Overview
This PR restructures the
dataframe-expectationscodebase to improve maintainability, clarity, and follows better Python package organisation patterns. This is a breaking change that reorganises the module structure while maintaining full backward compatibility of the user-facing API.Most of the restructuring affects internal files. For users the only migration needed would be to update the
DataFrameExpectationsSuiteimport.Before:
After:
Module Reorganisation
Before:
After:
Moving forward we use the following guidelines:
core/- Framework internals (base classes, types, utilities)expectations/- Expectation implementations organized by typeregistry.py,suite.py) - Public APIsRegistry refactoring
In addition to reorganising the code structure, the registry has also been refactored, where I consolidated 3 separate dictionaries into 2 optimised structures.
Version Management
Implemented robust version handling using
importlib.metadata:Checklist