feature/INT-1631 - updates the handling file purposes in the codebase#600
Merged
Conversation
|
armando-rodriguez-cko
approved these changes
May 21, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 updates the handling of file purposes in the codebase to use a type-safe enum instead of raw strings, and adds support for additional file purposes. The changes improve code reliability and clarity by enforcing the use of the
FilePurposeenum throughout the code and by expanding the recognized file purposes.File Purpose Handling Improvements:
purposefield inFileDetailsResponsefrom aStringto theFilePurposeenum, ensuring type safety and consistency.FilePurposeenum to include new purposes:ARBITRATION_EVIDENCEandSUBMITTED_EVIDENCE, with appropriate serialization annotations for JSON mapping.Test Adjustments:
DisputesTestIT.javaandprevious/DisputesTestIT.javato compareFilePurposeenum values directly instead of comparing strings, reflecting the new type-safe approach. [1] [2]