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.
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
HCMPRE-470 validation changes for assumptions #902
HCMPRE-470 validation changes for assumptions #902
Changes from 3 commits
00feaee
1048d45
985fd63
4a90d7a
54538bc
9fc5f1e
d6bb7d3
dba72d4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Refactor to improve type safety by specifying a consistent return type
The method
extractFieldsFromAdditionalDetails
currently returns anObject
, which could be aList<String>
,Integer
,Boolean
,String
, or even aJsonNode
. This approach can lead to confusion and potential runtime errors for callers, as they need to perform type checks and casts based on the returned value.Consider refactoring the method to return a more specific type or use generics to enhance type safety and clarity. For example, you could parameterize the method to return a specified type based on the expected field content.
Apply the following changes to specify the return type using generics:
This change allows callers to specify the expected return type, enhancing usability and reducing the need for type checks.
📝 Committable suggestion