API non existing values #208

Closed
opened 2022-09-28 09:34:10 +02:00 by mpeltriaux · 1 comment
Owner

Status quo

If a KonovaCode is used, which does not exist, the Response looks like this:

{
    "errors": [
        "KonovaCode matching query does not exist."
    ]
}

Enhancement

It would be better if the unresolved atomId would be returned as well, like:

{
    "errors": [
        "KonovaCode matching query does not exist: 12345"
    ]
}
# Status quo If a KonovaCode is used, which does not exist, the Response looks like this: ```json { "errors": [ "KonovaCode matching query does not exist." ] } ``` # Enhancement It would be better if the unresolved atomId would be returned as well, like: ```json { "errors": [ "KonovaCode matching query does not exist: 12345" ] } ```
mpeltriaux added the
enhancement
label 2022-09-28 09:34:10 +02:00
mpeltriaux self-assigned this 2022-09-28 09:34:10 +02:00
Author
Owner

Proper response

The proper response has been implemented and will display the wrong atomId as well as the list identifier to clarify which list has been used as lookup:

{
    "errors": [
        "KonovaCode matching query does not exist. (7101318 not found in official list 907)"
    ]
}

Merged in #212

# Proper response The proper response has been implemented and will display the wrong atomId as well as the list identifier to clarify which list has been used as lookup: ```json { "errors": [ "KonovaCode matching query does not exist. (7101318 not found in official list 907)" ] } ``` # Merged in #212
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: IT-Naturschutz/konova#208
No description provided.