hola_api's Introduction

Hi there 👋

I'm a System Engineer (DevOps Engineer/Site Reliability Engineer call it as you wish). I'm from Russia, but living in the Netherlands. You can find me on Twitter, or on LinkedIn.

✍ Blog & Writing

Apart from engineering, I also maintain a blog, currently only in Russian. You can find my articles on my website at doam.ru.

🔧 Technologies & Tools

hola_api's People

Watchers

hola_api's Issues

Return user info in task and tasks in user ?

Respond with json error

when respond with error, wrap it like:
{"error":"Validation error"}
in perfect case an error object MAY have the following members:

id: a unique identifier for this particular occurrence of the problem.
links: a links object containing the following members:
about: a link that leads to further details about this particular occurrence of the problem.
status: the HTTP status code applicable to this problem, expressed as a string value.
code: an application-specific error code, expressed as a string value.
title: a short, human-readable summary of the problem that SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.
detail: a human-readable explanation specific to this occurrence of the problem. Like title, this field's value can be localized.
source: an object containing references to the source of the error, optionally including any of the following members:
pointer: a JSON Pointer [RFC6901] to the associated entity in the request document [e.g. "/data" for a primary data object, or "/data/attributes/title" for a specific attribute].
parameter: a string indicating which URI query parameter caused the error.
meta: a meta object containing non-standard meta-information about the error.