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

1750: Endpoint specification for verein360 #1773

Merged
merged 2 commits into from
Nov 20, 2024

Conversation

ztefanie
Copy link
Member

@ztefanie ztefanie commented Nov 14, 2024

Short description

Added documentation we can sent to verein360. As soon as this PR is approved I will send this documentation to Verein360. The deadline for this is end of november.

Testing

you can call the endpoint as specified and check if this works as expected.

Resolved issues

Fixes: #1750

@ztefanie ztefanie changed the base branch from main to 1623-add-i18n-for-administration November 14, 2024 10:10
@ztefanie ztefanie changed the title 1750 endpoint specification for verein360 1750: Endpoint specification for verein360 Nov 14, 2024
Base automatically changed from 1623-add-i18n-for-administration to main November 18, 2024 08:47
Copy link
Member

@steffenkleinle steffenkleinle left a comment

Choose a reason for hiding this comment

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

I am not really sure of the context of this doc, but perhaps it makes sense to add a little more information on the used types? E.g. that dates need to be ISO8601 date strings.
Depending on the context my comments might be unnecessary.

docs/verein360-enpoint.md Outdated Show resolved Hide resolved
docs/verein360-enpoint.md Outdated Show resolved Hide resolved
docs/verein360-enpoint.md Outdated Show resolved Hide resolved
docs/verein360-enpoint.md Outdated Show resolved Hide resolved
"organization": {
"address": {
"country": {
"shortText": "Germany"
Copy link
Member

Choose a reason for hiding this comment

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

❓ Why are these shortText attributes needed?
Not sure about this one:

Suggested change
"shortText": "Germany"
"shortText": "Deutschland"

Copy link
Contributor

Choose a reason for hiding this comment

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

if you send an application you can check the actual payload. But good question why this was implemented like this, maybe @michael-markl can give some input

docs/verein360-enpoint.md Show resolved Hide resolved
docs/verein360-enpoint.md Outdated Show resolved Hide resolved
Copy link
Contributor

@f1sh1918 f1sh1918 left a comment

Choose a reason for hiding this comment

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

For me this looks good. Just checked the payload.
Two minor things:

  1. We should clarify how we get the "source" of application. But as i commented this can also be applied via the api token. I think thats better than provide here an optional string field.
  2. I would just add some comments to the dates (format : yyyy-mm-dd f.e.)

"organization": {
"address": {
"country": {
"shortText": "Germany"
Copy link
Contributor

Choose a reason for hiding this comment

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

if you send an application you can check the actual payload. But good question why this was implemented like this, maybe @michael-markl can give some input

docs/verein360-enpoint.md Show resolved Hide resolved
Copy link
Member

@steffenkleinle steffenkleinle left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -7,9 +7,9 @@ All details about the endpoint can be found in the [API Documentation](../specs/

## Usage

### Set Authourization Header
### Authourization Header
Copy link
Member

Choose a reason for hiding this comment

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

🙃 Typo

Suggested change
### Authourization Header
### Authorization Header

@ztefanie ztefanie merged commit 6f91edf into main Nov 20, 2024
1 check passed
@ztefanie ztefanie deleted the 1750-endpoint-specification-for-verein360 branch November 20, 2024 09:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Send final endpoint specification to verein360
3 participants