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

NIAD-3234: endpoint docs update #1024

Merged
merged 4 commits into from
Dec 6, 2024
Merged

NIAD-3234: endpoint docs update #1024

merged 4 commits into from
Dec 6, 2024

Conversation

ole4ryb
Copy link
Collaborator

@ole4ryb ole4ryb commented Dec 5, 2024

What

Endpoints documentation update

Why

The documentation must remain synchronized with the code implementation to ensure accuracy, clarity, and ease of use. This alignment minimizes confusion, reduces the risk of errors during integration, and provides developers with reliable information to effectively utilize the API.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Internal change (non-breaking change with no effect on the functionality affecting end users)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated the Changelog with details of my change in the UNRELEASED section if this change will affect end users

@ole4ryb ole4ryb enabled auto-merge (squash) December 5, 2024 11:49
Comment on lines +14 to +19
parameters:
- name: request
in: query
required: true
schema:
$ref: '#/components/schemas/EhrStatusRequestQuery'
Copy link
Collaborator

Choose a reason for hiding this comment

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

For my understanding, is this saying you can pass the filtering parameters in via query parameters? Also it's a bit strange it's marked as required, given that I don't think I've ever used the /requests endpoint in this way. 🤔

toAsid: "200000000359"
fromOdsCode: "P883302"
toOdsCode: "P113302"
required: true
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hmm, I'm pretty sure I've also called this endpoint without specifying a request body and it's worked. 🤔

README.md Outdated Show resolved Hide resolved
Any "in-progress" transfers are excluded from this list, but become available once they either succeed or fail.

Requests can be made to the following endpoint, where each attribute within the JSON POST body is an optional filter criteria.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Related to my comments below about required, this comment reaffirms my understanding which is that the filtering is optional.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

ok, I see, make sense, I will look into it and adjust it

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think as object it is required but EhrStatusRequestQuery object has fields which are not mandatory and can be empty.

README.md Show resolved Hide resolved
Copy link

github-actions bot commented Dec 5, 2024

Looks good. No mutations were possible for these changes.
See https://pitest.org

Copy link

sonarqubecloud bot commented Dec 5, 2024

@ole4ryb ole4ryb merged commit fece70a into main Dec 6, 2024
16 checks passed
@ole4ryb ole4ryb deleted the NIAD-3234-docs branch December 6, 2024 10:43
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