switch on wldb package for models #68
Merged
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 pull request refactors the codebase to use the new
welearn_databasepackage for all database models and enumerations, replacing the previouswelearn_datastack.data.db_modelsand related imports. It also updates test fixtures and document content strings for improved clarity and consistency. These changes ensure better modularity, maintainability, and compatibility with the updated database package.Migration to
welearn_databasepackage:Replaced all imports of
welearn_datastack.data.db_modelsand related enumeration modules with corresponding imports fromwelearn_database.data.modelsandwelearn_database.data.enumerationacross all test and utility files. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]Added
welearn-database = "^0.2.5"as a dependency inpyproject.tomlto support the new database package.Test data and fixtures updates:
Updated test document content strings to use more realistic and varied sample text instead of generic placeholders, improving test clarity and robustness. [1] [2] [3] [4] [5] [6] [7] [8] [9]
Removed unused or unnecessary imports, such as
Mock, where not needed, and cleaned up test setup code for better readability. [1] [2]General code consistency:
These changes collectively modernize the codebase, streamline database interactions, and enhance test reliability.