Forum Discussion

chichepo's avatar
chichepo
Champion Level 3
2 years ago
Solved

SwaggerHub Editor - Path line length not resolved correctly in YAML

Hi All,

 

I got a Yaml file that includes an endpoint with a path length longer than 130 characters.
...

paths:
     /something_very_long/something_very_long/something_very_long/something_very_long/something_very_long/something_very_long/list:
        get:

...
When loaded within SwaggerHub , the documentation rendering is OK.
When generating a Server Stub, it's OK
When exporting the file to resolved JSON, it's OK

When exporting the file to resolved YAML it generates weird characters and I have to fix the file before using it. 

...

paths:
   ?  /something_very_long/something_very_long/something_very_long/something_very_long/something_very_long/something_very_long/list:
     :   get:

...

 

Is there any ways to make the Yaml resolve working with long paths?

  • chichepo's avatar
    chichepo
    2 years ago

    I finally found the root cause for this issue:

    SwaggerHub IDE, for Yaml, limits the path length to 128 char. 

    I am working with SwaggerHub version 1.27.0-76 (On-premise)

     

    So, when the path is longer than 128 char. and is resolved, it generates weird characters.
    There is no other way to deal with this issue other than limiting the path length.

1 Reply

Sort By
  • chichepo's avatar
    chichepo
    Champion Level 3
    2 years ago

    I finally found the root cause for this issue:

    SwaggerHub IDE, for Yaml, limits the path length to 128 char. 

    I am working with SwaggerHub version 1.27.0-76 (On-premise)

     

    So, when the path is longer than 128 char. and is resolved, it generates weird characters.
    There is no other way to deal with this issue other than limiting the path length.