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

[MODFIN-346] - Implement unrelease encumbrance endpoint #220

Merged
merged 6 commits into from
Jan 9, 2024

Conversation

azizbekxm
Copy link
Contributor

Purpose

https://issues.folio.org/browse/MODFIN-346

Approach

Endpoint will be implemented
Unit tests were written

TODOS and Open Questions

Learning

Pre-Merge Checklist:

Before merging this PR, please go through the following list and take appropriate actions.

  • Does this PR meet or exceed the expected quality standards?
    • Code coverage on new code is 80% or greater
    • Duplications on new code is 3% or less
    • There are no major code smells or security issues
  • Does this introduce breaking changes?
    • Were any API paths or methods changed, added or removed?
    • Were there any schema changes?
    • Did any of the interface versions change?
    • Were permissions changed, added or removed?
    • Are there new interface dependencies?
    • There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

  • What other modules will these changes impact?
  • Do JIRAs exist to update the impacted modules?
    • If not, please create them
    • Do they contain the appropriate level of detail? Which endpoints/schemas changed, etc.
    • Do they have all the appropriate links to blocked/related issues?
  • Are the JIRAs under active development?
    • If not, contact the project's PO and make sure they're aware of the urgency.
  • Do PRs exist for these changes?
    • If so, have they been approved?
  • Did you modify code to call some additional endpoints?
    • If so, do you check that necessary module permission added in ModuleDescriptor-template.yaml file?

Ideally, all the PRs involved in breaking changes would be merged on the same day
to avoid breaking the folio-testing environment.
Communication is paramount if that is to be achieved,
especially as the number of inter-module and inter-team dependencies increase.

While it's helpful for reviewers to help identify potential problems,
ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

@azizbekxm azizbekxm marked this pull request as draft January 8, 2024 12:20
@azizbekxm azizbekxm self-assigned this Jan 8, 2024
@azizbekxm azizbekxm marked this pull request as ready for review January 8, 2024 14:27
@azizbekxm azizbekxm requested a review from a team January 8, 2024 14:28
@@ -36,4 +37,12 @@ public void postFinanceReleaseEncumbranceById(String id, Map<String, String> oka
.onFailure(fail -> handleErrorResponse(asyncResultHandler, fail));
}

@Override
@Validate
public void postFinanceUnreleaseEncumbranceById(String id, Map<String, String> okapiHeaders,
Copy link
Contributor

Choose a reason for hiding this comment

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

Will repeated call throw an exception?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Probably no, I used approach from release encumbrance feature

Copy link

sonarqubecloud bot commented Jan 9, 2024

@azizbekxm azizbekxm merged commit 1ef1dfa into master Jan 9, 2024
6 checks passed
@azizbekxm azizbekxm deleted the MODFIN-346 branch January 9, 2024 14:37
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.

4 participants