Swagger-ui: Option to suppress "default" title

[stevage]

I'm not entirely sure what this word "default" refers to (or in what situation you'd have more than one resource), but when you only have one it's kind of confusing and ugly:

Perhaps either never show it if there's only one, or allow an option for removal?

I ended up forcibly hiding it with CSS:

  .resource .heading h2 {
    display:none !important;
  }

[webron]

@stevage - Swagger 2.0 introduced a new tagging system to allow operation grouping.

The default is just the default group used for all operations that are tag-less as they need to show up somewhere. If you have other suggestions, we'd be happy to hear.

[stevage]

Ok, thanks - I didn't know about tags.

Suggestions:

• if there no tags at all, don't show "default" - show nothing
• if the "default" tag is always shown first (I don't know if true), then maybe you don't show any text for it.
• maybe "General" or "Untagged" would be better terms than "default".

For my own case, now that I know you can tag, I don't want to hide it anymore :)

[ponelat]

We can write in a clause and option for swagger-ui that would show/hide this 'default' tag.

Out of curiosity, what would happen if you were to create a tag called 'default', would untagged resources end up merged into it?

[webron]

@ponelat - do I _need_ to make a snarky comment here? ;)

[howarddierking]

:+1: to this - took me a few minutes today to figure out exactly why I kept seeing "default" everywhere

[prusswan]

I wouldn't mind configuring options for a "default" tag, but this does not seem to be part of the specifications..

[andrewzk]

+1

[deckar01]

I was about to start testing strategies for this issue, but I tagged my API instead. Much better than having everything in one big "default" group. :wink:

Maybe the untagged operations belong below the tagged groups in an uncollapsable container. This would avoid issues with the default group name colliding with a tag name.

The tags field for operations is actually being assigned a default value by swagger-js when the tag list is empty. I think https://github.com/swagger-api/swagger-ui/issues/605 incorrectly fixed a UI bug by patching swagger-js.

Since the spec doesn't require operations to have tags and doesn't document a default value, I am opening an issue for swagger-js.

[webron]

Closing as we're not going to implement it. If anyone wants to submit a PR to that effect, we'll be happy to review.