Francois LASNE

My feedback

  1. 216 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  7 comments  ·  API Management » Service management  ·  Flag idea as inappropriate…  ·  Admin →
    Francois LASNE commented  · 

    this brings an enhancement of the quality as an API.
    Still this should be a handle by feature tag , meaning you want to enable or disable it
    the right location for that would be a policy for it

    Francois LASNE supported this idea  · 
  2. 88 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  API Management  ·  Flag idea as inappropriate…  ·  Admin →
    Francois LASNE commented  · 

    second level of correction support recursive reference , here is a use case ,
    recursion is here to provide the call stack pattern ,

    here you have an error with a field cause that is as well an error

    this use case is supported into swagger.io ( there was some bug in the past ) but is not ok in APIM

    "Error": {
    "type": "object",
    "description": "The RFC 7807 defined Problem Details for HTTP APIs , is as of today proposed standard, and it SHOULD be applied. It proposes a seamless structure for common pattern of errors as same as an extension mechanism",
    "required": [
    "title"
    ],
    "properties": {
    "type": {
    "type": "string",
    "description": "A URI reference [RFC3986] that identifies the problem type"
    },
    "title": {
    "type": "string",
    "description": "A short human-readable summary of the problem type"
    },
    "status": {
    "type": "string",
    "description": "The HTTP status code generated by the origin server for this occurrence of the problem"
    },
    "details": {
    "type": "string",
    "description": "A human-readable explanation specific to this occurrence of the problem"
    },
    "instance": {
    "type": "string",
    "description": "A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced"
    },
    "cause": {
    "$ref": "#/definitions/Error"
    }
    }
    }

  3. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  API Management » Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
    Francois LASNE commented  · 

    I agree this would be a very usefull feature , we need to add for instance phone number, country etc.

    Francois LASNE supported this idea  · 

Feedback and Knowledge Base