refactor: Phase 16d - Remove IdentifiedObject mappings from MapStruct mappers #86
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.
Summary
Phase 16d completes the separation of concerns between MapStruct mapping (XSD fields only) and Atom protocol handling (IdentifiedObject metadata). This refactor removes all IdentifiedObject field mappings from MapStruct mappers and fixes related DTOs and tests.
Mapper Changes (17 mappers)
updateEntity()methods from all mappers@Mapping(target = "id", ignore = true)to prevent UUID→Long type conflictsUpdated Mappers:
DTO Fixes
UsageSummaryDto
ElectricPowerQualitySummaryDto
Test Enhancements
DtoExportServiceImplTest
Test Results
Files Changed
Impact
This change completes the architectural separation:
The separation prevents type conflicts (UUID vs Long for id), reduces mapper complexity, and properly delegates metadata handling to the AtomFeedDto/AtomEntryDto layer.
🤖 Generated with Claude Code