jschalk / jaar

Cross-cultural communication engine built on customizable economic systems. Produces personalized agendas, calendars, finance reports for users.
0 stars 1 forks source link

#358 cleanup #367

Closed jschalk closed 3 weeks ago

jschalk commented 3 weeks ago

Summary by Sourcery

Clean up test files by updating assertions to reflect correct data types and string positions, and remove obsolete commented-out code.

Enhancements:

Chores:

sourcery-ai[bot] commented 3 weeks ago

Reviewer's Guide by Sourcery

This PR contains cleanup changes across multiple test files and implementation files. The main changes involve updating data type references from 'FISCAL' to 'REAL' in database-related code, adjusting test assertions for SQL string positions, and adding a skeleton for a new brick dataframes function. There's also some commented-out test code that appears to be work in progress.

Class diagram for updated data type references

classDiagram
    class TestAtomConfig {
        +test_get_normalized_bud_table_build_ReturnsCorrectObj()
        -FISCAL
        +REAL
    }
    class TestNormalModels {
        +all_columns_are_as_config_requires(mapper, config_category)
        +print_out_expected_class_attribute_declarations(config_category)
        -FISCAL
        +REAL
    }

Class diagram for new brick dataframes function

classDiagram
    class WorldTool {
        +get_all_excel_bricksheets(dir: str) : set[str, str, str]
        +get_all_brick_dataframes()
    }

File-Level Changes

Change Details Files
Changed database column type from 'FISCAL' to 'REAL' in multiple locations
  • Updated SQLite data type from 'FISCAL' to 'REAL' in normalized budget table configuration
  • Modified type conversion logic to handle 'REAL' instead of 'FISCAL' when mapping to Float
src/f04_gift/test_atom/test_atom_config.py
src/f04_gift/test_normal_models/test_normal_models.py
Updated SQL string position assertions in tests
  • Modified expected position of 'example_item_reasonunit_str' from 3441 to 3417
  • Changed expected position of 'end_sqlstr' from 5436 to 5384
  • Updated expected position of another 'example_item_reasonunit_str' from 3473 to 3449
src/f07_fiscal/test_fiscal_/test_journal_sqlstr_.py
Added new brick dataframes functionality skeleton
  • Added empty function definition for get_all_brick_dataframes
  • Added commented-out test case for get_all_brick_dataframes function
src/f10_world/world_tool.py
src/f10_world/test/test__world_tool.py

Tips and commands #### Interacting with Sourcery - **Trigger a new review:** Comment `@sourcery-ai review` on the pull request. - **Continue discussions:** Reply directly to Sourcery's review comments. - **Generate a GitHub issue from a review comment:** Ask Sourcery to create an issue from a review comment by replying to it. - **Generate a pull request title:** Write `@sourcery-ai` anywhere in the pull request title to generate a title at any time. - **Generate a pull request summary:** Write `@sourcery-ai summary` anywhere in the pull request body to generate a PR summary at any time. You can also use this command to specify where the summary should be inserted. #### Customizing Your Experience Access your [dashboard](https://app.sourcery.ai) to: - Enable or disable review features such as the Sourcery-generated pull request summary, the reviewer's guide, and others. - Change the review language. - Add, remove or edit custom review instructions. - Adjust other review settings. #### Getting Help - [Contact our support team](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).