Uploaded image for project: 'Couchbase Documentation'
  1. Couchbase Documentation
  2. DOC-6017

Sync Gateway: API references 'default' section not opening

    XMLWordPrintable

Details

    Description

      On both the public and admin REST API references, clicking on the 'default' heading does not open anything. All other sections work OK.

       

      Tested in Firefox 71.0b10 and Safari 13.0.3

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            Ian.bridge Ian Bridge added a comment -

            Ben - is this still the case? I tried it just on Safari 13.0.3 and Chrome. Both work fine. 

             

            Ian.bridge Ian Bridge added a comment - Ben - is this still the case? I tried it just on Safari 13.0.3 and Chrome. Both work fine.   
            ben.brooks Ben Brooks added a comment -

            Hi, I'm still not able to open the default section on either Firefox or Safari. No errors appear in the javascript console.

            I tested it in Google Chrome and it does work as expected.

            ben.brooks Ben Brooks added a comment - Hi, I'm still not able to open the default section on either Firefox or Safari. No errors appear in the javascript console. I tested it in Google Chrome and it does work as expected.
            Ian.bridge Ian Bridge added a comment -

            Ben Brooks can you clarify, please? Are you saying that selecting API REFERENCES neither expands nor collapses the topic group? Or that selecting it does not display a topic?

            The latter is an (annoying) but integral feature; provision of content for the category headers is optional.

            The former would be a bug, but it is not one I can observe in Chrome 79.0.3945, Firefox 72.0.2 or Safari 13.0.4. 

            Ian.bridge Ian Bridge added a comment - Ben Brooks  can you clarify, please? Are you saying that selecting  API REFERENCES  neither expands nor collapses the topic group? Or that selecting it does not display a topic? The latter is an (annoying) but integral feature; provision of content for the category headers is optional. The former would be a bug, but it is not one I can observe in Chrome 79.0.3945, Firefox 72.0.2 or Safari 13.0.4. 
            Ian.bridge Ian Bridge added a comment -

            Ben Brooks  Sorry I was a bit slow grasping the context. 

            I've looked at the yaml for this. At 2.1 the default category contained only a db_revs_diffs property. This had no tag to associate it to a category. At 2.5 a tag: database was added to db_revs_diffs, allowing it to be correctly grouped under the database category but now leaving default empty; hence although it does expand, its expanded content is nil.

            I don't know why, yet, we are showing the empty category and continue to investigate.

            Ian.bridge Ian Bridge added a comment - Ben Brooks   Sorry I was a bit slow grasping the context.  I've looked at the yaml for this. At 2.1 the  default category contained only a db_revs_diffs property. This had no tag to associate it to a category. At 2.5 a tag: database was added to db_revs_diffs , allowing it to be correctly grouped under the database category but now leaving default empty; hence although it does expand, its expanded content is nil. I don't know why, yet, we are showing the empty category and continue to investigate.
            Ian.bridge Ian Bridge added a comment -

            Ben Brooks Jay Vavachan As this is a duplicate of DOC-5401 I am going to close this and progress a resolution on DOC-5401 (Release 2.5), which is when the issue first became noticeable. Although at the moment it is looking like a 'feature' of Swagger. 

            It seems the ‘default’ tag is a catchall that is output to cover any untagged operations (endpoints) and that it is output regardless of there being any or not

            That being the case we may need to address it in CSS.

            Ian.bridge Ian Bridge added a comment - Ben Brooks Jay Vavachan As this is a duplicate of DOC-5401  I am going to close this and progress a resolution on DOC-5401 (Release 2.5), which is when the issue first became noticeable. Although at the moment it is looking like a 'feature' of Swagger.  It seems the ‘default’ tag is a catchall that is output to cover any untagged operations (endpoints) and that it is output regardless of there being any or not https://github.com/swagger-api/swagger-ui/issues/1311 https://github.com/swagger-api/swagger-ui/issues/4879 That being the case we may need to address it in CSS.
            Ian.bridge Ian Bridge added a comment -

            Resolution to be progressed on original ticket - DOC-5401

             

            Ian.bridge Ian Bridge added a comment - Resolution to be progressed on original ticket - DOC-5401  
            Ian.bridge Ian Bridge added a comment -

            See also DOC-5401

            Ian.bridge Ian Bridge added a comment - See also DOC-5401
            Ian.bridge Ian Bridge added a comment -

            Closed. No resolution here. See DOC-5401 for any further updates.

            Ian.bridge Ian Bridge added a comment - Closed. No resolution here. See DOC-5401 for any further updates.

            People

              Ian.bridge Ian Bridge
              ben.brooks Ben Brooks
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty