-
Notifications
You must be signed in to change notification settings - Fork 66
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
Api 41369 remove v1 base method bgs ext #19620
Changes from 11 commits
5918d16
e6147da
58c5d40
655f0c9
af89f46
e2f0d4f
5210653
6575479
3f047a3
6032b6f
4fa545f
c7c429f
849b3be
6b41d96
dffabf6
c3ee1a3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
# frozen_string_literal: true | ||
|
||
module ClaimsApi | ||
class StandardDataService < ClaimsApi::LocalBGS | ||
def bean_name | ||
'StandardDataService' | ||
end | ||
|
||
def get_contention_classification_type_code_list | ||
body = Nokogiri::XML::DocumentFragment.parse <<~EOXML | ||
<getContentionClassificationTypeCodeList/> | ||
EOXML | ||
Comment on lines
+10
to
+12
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. should we redis cache this? I'm not sure if these change frequent enough for us to need to make this call per request? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Revisiting this, I got this call confused with one in the other PR I have, I think we probably could benefit from caching this in Redis |
||
|
||
response = make_request(endpoint: bean_name, action: 'getContentionClassificationTypeCodeList', body:) | ||
response[:return] | ||
end | ||
end | ||
end |
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.
Tyler had a similar question on the CorporateUpdateWebService PR: Should this be StandardDataServiceBean/StandardDataService or similar, for consistency with our other services?
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.
Ah yep, I can see this now, going to start a discussion on this since looking at the catalog I'm not sure all of these will be exactly the same set up/structure (note the difference in the image between my service here and another one that appears to have that top level at the ....ServiceBean/`
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.
@mchristiansonVA I feel like the answer to your question here is 'no' but worth making sure so I'll kick off a thread to discuss
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.
Oh, I think what I was overlooking is that they may both be the same, which is a little confusing to me but maybe
StandardDataService/StandardDataService
is what I need hereThere 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.
in line with slack discussion adjusted the
bean_name
c3ee1a3Good callout @mchristiansonVA to help keep these consistent