2 Matching Annotations
  1. Sep 2022
  2. jonathancrozier.com jonathancrozier.com
    Base your API error response model on a solid standard with the Problem Details RFC - Jonathan Crozier
    1
    1. TylerRick 26 Sep 2022
      For example, let’s consider the type property. For most of the projects I am working on, it isn’t practical to have a webpage dedicated to each type of possible error.

      That's not required. The standard doesn't require this to be a URL locator — merely a URI! So you can just make up a URI and use it even if it's not resolvable. ... like you did for the URN below.

      misunderstanding web APIs: Problem Details URI forgive their ignorance/mistake/misunderstanding
    Visit annotations in context

    Tags

    Annotators

    URL

    jonathancrozier.com/blog/base-your-api-error-response-model-on-a-solid-standard-with-the-problem-details-rfc
  3. Feb 2021
  4. trailblazer.to trailblazer.to
    Trailblazer - Blog
    1
    1. TylerRick 23 Feb 2021
      So, whenever you hear the medieval argument “Trailblazer is just a nasty DSL!”, forgive your opponent, you now know better. The entire framework is based on small, clean Ruby structures that can be executed programmatically.
      funny debate forgive their ignorance/mistake/misunderstanding
    Visit annotations in context

    Tags

    Annotators

    URL

    trailblazer.to/2.1/blog.html