DO NOT MERGE - TPX PoC code #522
Draft
Conversation
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
…ctions This commit introduces new Django models for the my_hr, payroll, and transactions apps. Corresponding migrations have been created to support these models. The settings have also been updated to include these new apps.
Refactored module and directory names for consistency and clarity. Added new modules for CSV and Excel file processing, S3 output, services, and serializers. Improved exception handling and logging functionality across the project.
Rename `myhr` module to `hr`, update model definitions, and implement CSV parsing methods. Revise URL routing to add `sns_notification` endpoint and update file processing logic. Adjust configurations and settings, ensuring compatibility with new structure and functionalities.
Introduce the ZeroTransaction model with fields for financial entries and a CSV parser method. Also, add necessary initial Django app configuration and placeholder files for admin, views, and tests.
This commit deletes the entire app_layer module, including admin configuration, apps settings, file processors for CSV and Excel, custom exceptions, logging services, models, serializers, service layer, URL routes, and views. The removal streamlines the codebase by eliminating unused or deprecated components.
Added console.log statements for debugging table_data and payroll_data in respective components. Refactored the payroll models by introducing new models and updating serializers accordingly, while cleaning up unnecessary code in templates and serialization logic.
Deleted the initial payroll migration files to tidy up database setup. Modified frontend components to include monthly payroll data handling, and introduced a new PayrollTableCell component for displaying monthly data in the PayrollTable. Enhanced backend data serializers and models to support these changes.
This commit introduces the initial migration for the payroll app, creating four models: EmployeePayroll, ForcastPayroll, NonEmployeePayroll, and Payroll. These models define the structure and fields for handling payroll data in the application.
Updated various Payroll components and variables to be specific to employees. This includes renaming files, functions, and properties to reflect the new naming convention and improve code clarity. Additionally, removed unused imports and redundant code.
Introduce a new component for managing non-employee payroll data. This update includes creating new components for editing and displaying non-employee payroll information, updating the context in the backend, and adjusting the frontend React entry points and templates.
Ensure PayrollTable and PayrollNonTable components map data correctly by matching rowIndex with data index. Added console logs in processPayrollData for debugging.
Deleted models, migrations, and related files for HR, Transaction, and ZeroTransaction modules. Consolidated functionalities into the payroll module, implemented new file processors, and updated relevant settings.
Deleted the log service module and initial migration script from the payroll directory. Removed obsolete HR model from payroll.models and refactored CsvFileProcessor and related modules to use the revised Payroll model.
Implemented functionality to post payroll edits and handle non-employee payroll data. This includes new views, forms, serializers, and URL patterns to support these features, as well as refactoring existing models and functions.
Refactored state management to distinguish between employee and non-employee payroll cells. Introduced new reducers, components, and utility functions to handle payroll and non-payroll data independently. Updated UI and data processing logic for better organization and maintainability.
…tables This update introduces distinct states for selected rows in employee and non-employee tables. The reducers and components have been updated to handle these new states, ensuring that selecting a row in one table type does not affect the selection in the other. This change improves the data handling and user interface clarity.
Added `nonEmployeeSelectedRow` and `employeeSelectedRow` resets in `SELECT_ALL` and `UNSELECT_ALL` actions to ensure proper state management for different row types. This change enhances the clarity of the selected row handling mechanism.
Introduce initial migrations and models for HR and Payroll apps. This includes creating models for EmployeePayroll, ForecastPayroll, HR, and NonEmployeePayroll, along with functionalities for parsing CSV data from S3 and updating records.
Updated payroll table and cell components to streamline ID generation and data validation logic. Improved processing of payroll data in backend and removed unnecessary console logs. Refactored form handling in Django to simplify data cleaning.
Detailed docstrings have been added to various files within the payroll module including models, views, serializers, and forms. These docstrings provide comprehensive explanations of class attributes, methods, and overall functionality to improve code readability and maintainability.
Added the cost_centre_code field to the EmployeePayroll and NonEmployeePayroll models and updated the related functions to use this field. Changed DecimalField to FloatField for the basic_pay, superannuation, and ernic fields across the models and relevant methods.
Added new migration for HRModel, and made corresponding changes to the models and serializers. Enhanced state management in the front end to support new MyHR functionality, added MyHREmployee components, views, and templates for displaying MyHR data.
Introduced new `CostCentreView` with corresponding URL path, view logic, and template. Updated `DirectorateView` and frontend components to handle dynamic view switching between directorate and cost centre. Enhanced frontend state management to accommodate these changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
DO NOT MERGE - just useful as a diff browser