Skip to content
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

EE-1082: Update OI API Intergration URLS #14

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mricher2000
Copy link
Collaborator

@mricher2000 mricher2000 commented Apr 19, 2024

Ticket

EE-1082

Changes

  • Updating the URLs so that they reflect the OI API updates here.

Definition of Done

  • Pull request is up to date with the destination branch
  • Commits were squashed
  • All Tests are passing
  • At least one code review
  • Screen-Review passed and logged.

Comment on lines 2 to 8
module Entities
class Payment < Base
def index(opts = {})
request(:get, "/supplier/#{supplier_uuid}/payment", opts)
request(:get, "/v1/supplier/#{supplier_uuid}/payment", opts)
end
end
end
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There were no updates in the docs regrading the payment API... so I am not sure if this needs to be updated? Wanted to check though.

@mricher2000
Copy link
Collaborator Author

A couple q's:

  • the base url in the docs has been updated - do we need to change anything on our end for this?
  • I also noticed that there is aVERSION here - should we update this?

@mricher2000 mricher2000 marked this pull request as ready for review April 19, 2024 18:53
@jgarciafundthrough
Copy link

@mricher2000 Does this PR need to go straight into master?

Copy link

@jgarciafundthrough jgarciafundthrough left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mricher2000 What do you think about have the version number as an environment variable and referencing the env variable through the code. Would make updating the version in the future less tedious as only 1 point of reference will need to be touched

@mricher2000
Copy link
Collaborator Author

@jgarciafundthrough Love the idea about having the version number as an env var. As it was pretty tedious going through & updating all the urls 😅 I will make that change!

Also I don't think it needs to go straight into master... I just didn't see a dev branch?

@jgarciafundthrough
Copy link

@mricher2000 oh weird ok. Maybe we can ask the team to see if anyone has worked with the gem before. Daniela might have some feedback/ideas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants