-
Notifications
You must be signed in to change notification settings - Fork 0
merging #88
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
Merged
Merged
merging #88
Conversation
This file contains hidden or 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
- Created a new migration to add the MasterFileRefNo column to the LandMiscellaneousMasterFiles table. - Updated existing records to populate MasterFileRefNo based on MasterFileNo. - Updated the AppDbContextModelSnapshot to reflect the new column. - Modified the LandMiscellaneousMasterFile model to include the MasterFileRefNo property.
branch update
- Created PasswordResets migration and updated model snapshot. - Implemented PasswordReset model to store OTP and related data. - Added IEmailSender interface and EmailSender service for sending emails. - Developed PasswordResetService to handle password reset requests, OTP generation, and verification. - Integrated EmailSender into PasswordResetService for sending OTP emails. - Updated Program.cs to register new services in the dependency injection container.
Add Password Reset functionality with OTP verification
Dev dulmini
- Introduced a new nullable foreign key column `LandMiscellaneousMasterFileId` in the `LMRentalEvidences` table. - Updated the `LMRentalEvidence` model to include the new foreign key and navigation property for `LandMiscellaneousMasterFile`. - Modified the DTOs to accommodate the new foreign key and added a DTO for `LandMiscellaneousMasterFile`. - Enhanced the repository interfaces and implementations to support fetching rental evidences by master file ID and reference number. - Updated the service layer to handle the new foreign key relationships and ensure proper data mapping. - Removed outdated sorting API documentation as it is no longer relevant.
branch sync
- Created migration for LALots table with foreign key to LandAquisitionMasterFiles. - Updated AppDbContextModelSnapshot to include LALots entity. - Added DTOs for LALot creation, update, and response. - Implemented LALot model with necessary properties and relationships. - Created AutoMapper profile for LALot mapping. - Defined ILALotRepository interface and implemented LALotRepository class. - Developed ILALotService interface and LALotService class for business logic. - Added methods for CRUD operations and validation in the service and repository layers.
…s, repositories, and services - Created a migration to add LandMiscellaneousMasterFileId to LMSalesEvidences, LMPastValuations, and LMBuildingRates tables. - Updated AppDbContextModelSnapshot to reflect new schema changes. - Modified LMBuildingRates, LMPastValuation, and LMSalesEvidence models to include LandMiscellaneousMasterFileId as a foreign key. - Enhanced DTOs for LMBuildingRates, LMPastValuation, and LMSalesEvidence to include LandMiscellaneousMasterFileId and related navigation properties. - Updated repositories to support fetching records by LandMiscellaneousMasterFileId and include related master file data. - Adjusted services to handle new methods for retrieving data based on LandMiscellaneousMasterFileId and to map master file details in response DTOs.
- Introduced new models for PastValuationsLA, BuildingRatesLA, SalesEvidenceLA, and RentalEvidenceLA coordinates. - Created corresponding DTOs for creating, updating, and responding with coordinate data. - Implemented repositories for managing coordinate data, including CRUD operations and report existence checks. - Developed services to handle business logic for coordinates, including validation and mapping to DTOs. - Updated the database context with new coordinate tables and relationships. - Added AutoMapper profiles for mapping between models and DTOs.
Dev dulmini
Enhance email formatting for password reset OTP notification
- Updated foreign key references in BuildingRatesLACoordinates, PastValuationsLACoordinates, RentalEvidenceLACoordinates, and SalesEvidenceLACoordinates to use specific IDs instead of ReportId. - Renamed columns and indices accordingly to reflect the new foreign key relationships. - Adjusted migration files to drop old foreign keys and add new ones. - Updated model snapshots to match the new schema. - Modified DTOs to replace ReportId with specific IDs for each coordinate type. - Refactored LACoordinates models to use new foreign key properties. - Updated AutoMapper profiles to ignore old Report references and map new relationships. - Changed repository interfaces and implementations to use new methods for fetching coordinates by specific IDs. - Updated service layer methods to reflect changes in repository methods and ensure correct validation for existence checks.
…nversion - Added migration to convert MasterFileId from string to int in PastValuationsLA table. - Introduced a temporary column for safe conversion and updated existing records. - Dropped the old string column and renamed the temporary column. - Ensured non-null constraint on MasterFileId with a default value for nulls. - Created index and foreign key constraint for MasterFileId referencing LandAquisitionMasterFiles. refactor(models): Update DTOs and entity models for MasterFileId type change - Changed MasterFileId property type from string to int in PastValuationsLADtos and PastValuationsLA model. - Added foreign key relationship in PastValuationsLA model for MasterFileId. chore(context): Add NeondbContext for PastValuationsLA - Created NeondbContext class for managing PastValuationsLA entity. - Configured model creating for PastValuationsLA with necessary indexes. feat(entity): Introduce PastValuationsLa entity - Added PastValuationsLa class to represent PastValuationsLA records with updated properties.
- Added a migration to convert the MasterFileId column in the BuildingRatesLA table from string to integer. - Introduced a temporary column for data conversion and ensured data integrity during the migration. - Updated the BuildingRatesLA model to reflect the new integer type for MasterFileId. - Modified DTOs for BuildingRatesLA to accommodate the change from string to int for MasterFileId. - Established foreign key relationship with LandAquisitionMasterFiles.
- Added a new migration to convert the MasterFileId column in the RentalEvidencesLA table from string to integer. - Introduced a temporary column for safe data migration and ensured data integrity by validating existing records against LandAquisitionMasterFiles. - Updated the RentalEvidenceLADtos and RentalEvidenceLA model to reflect the change in MasterFileId type. - Established foreign key relationship between RentalEvidencesLA and LandAquisitionMasterFiles.
- Added migration to convert MasterFileId from string to integer in SalesEvidencesLA table. - Updated related foreign key and index for MasterFileId. - Modified SalesEvidenceLADtos to reflect the change in MasterFileId type. - Adjusted SalesEvidenceLA model to include foreign key relationship with LandAquisitionMasterFile.
Dev jalina
…n key constraints - Added MasterfileId column to SalesEvidenceLACoordinates, RentalEvidenceLACoordinates, PastValuationsLACoordinates, and BuildingRatesLACoordinates tables. - Created indexes for MasterfileId in each of the above tables. - Established foreign key relationships between MasterfileId and LandAquisitionMasterFiles table with cascade delete behavior.
branch sync
- Updated the LACoordinates model to allow nullable foreign key properties for PastValuationId, BuildingRateId, SalesEvidenceId, and RentalEvidenceId. - Modified the corresponding migration to reflect these changes in the database schema. - Adjusted the AppDbContextModelSnapshot to match the new nullable properties. - Updated LACoordinateServices to set foreign key properties to null instead of 0 when creating new coordinates.
… for multiple coordinate types
Dev akith
Dev jalina
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.
No description provided.