-
Notifications
You must be signed in to change notification settings - Fork 1
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
MODLD-646: Update the response structure of authorityAssignmentCheck API #104
base: master
Are you sure you want to change the base?
Conversation
@@ -267,8 +267,7 @@ paths: | |||
content: | |||
text/plain: |
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.
Now it should be application/json, right?
Description is outdated too (line 266)
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.
Yes. Fixed.
"reason": { | ||
"type": "string", | ||
"enum": ["UNSUPPORTED_MARC", "NO_LCCN", "NOT_VALID_FOR_TARGET"], | ||
"description": "Indicates the reason why the assignment is not valid. Only present if 'validAssignment' is false." |
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.
Such description makes me feel that parameter name isn't so descriptive.
What if we name it like invalidationReason or smth?
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.
Good point. Copilot suggested the name 'invalidAssignmentReason'. So, I used it :)
5fdbd75
to
bc53fb6
Compare
Quality Gate passedIssues Measures |
Should be merged along with folio-org/ui-linked-data#84