To summarise progress so far:

The mobile rest api (public and admin) is showing an empty 'tag' default. This manifests as a default group that seems not to expand when clicked.

The issue became visible in Release 2.5. Prior to Release 2.5 the default tag showed a revs_diffs endpoint. But since that endpoint was properly tagged in 2.5 DOC-3851 the default is now empty.

From swagger documentation, 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

This may need to be addressed in CSS.

Ian Bridge, Jay Vavachan Is this a blocker issue?

Priya Rajagopal Jay Vavachan

I think it's a quirk, a possible minor distraction. It's a link that appears not to work because it has no content. I haven't found a way to suppress it, but maybe we can add a dummy entry in Default that states it is 'intentionally empty' or that 'No default entries are defined' so at least if anyone does click on it, they have an explanation. 

Any reason why we need to have that empty tag default ? If thats removed, then  this section wouldn't show

Also, not sure why this is was a Blocker issue  to begin with (In the bigger scheme of things , would appear far more pressing issues to be resolved. This is just an empty section that doesn't expand)

Ian Bridge unless you disagree, I view this as a minor issue...at most major issue.