Forum Discussion

dcee's avatar
dcee
New Contributor
8 years ago

Odd UI behaviour

I'm getting this message;   Semantic error at paths./domains/{crawl_id} Declared path parameter "crawl_id" needs to be defined as a path parameter at either the path or operation level Jump to li...
  • MarcusJ's avatar
    MarcusJ
    8 years ago

    Hi Dave,

     

    I have corrected your API.  The current problem was with the tags object (looks like you already corrected the previous error you described).  The tags object requires a name and can have a description as shown in the Swagger specification link below.   Using the summary field is not applicable for tags and was removed.  After correcting the tags object it was just indentation errors that needed to be corrected and now it's valid.

     

    http://swagger.io/specification/#operationObject

     

     

    Regards,

    Marcus

    SmartBear Support

MarcusJ's avatar
MarcusJ
Moderator

Hello,

 

Please let us know the API you are using so we can look further into this.  Also, if your API is private please make swaggerhub-support a collaborator, or fork it and make swaggerhub-support a collaborator.

 

Regards,

Marcus

SmartBear Support

dcee's avatar
dcee
New Contributor
8 years ago

Hi Marcus

 

I'd already added you guys as a collaborator and the API in question is called BbeeAPI

 

Thanks,


Dave

  • MarcusJ's avatar
    MarcusJ
    Moderator
    8 years ago

    Hi Dave,

     

    I have corrected your API.  The current problem was with the tags object (looks like you already corrected the previous error you described).  The tags object requires a name and can have a description as shown in the Swagger specification link below.   Using the summary field is not applicable for tags and was removed.  After correcting the tags object it was just indentation errors that needed to be corrected and now it's valid.

     

    http://swagger.io/specification/#operationObject

     

     

    Regards,

    Marcus

    SmartBear Support

    • dcee's avatar
      dcee
      New Contributor
      8 years ago

      Thanks, Marcus. I hadn't actually fixed the error... maybe it was a browser cache issue? In any case, it seems resolved now. 

       

      Cheers,

       

      Dave