Ability to disable TopbarPlugin via SwaggerUIBundle parameter

[tleyden]

There are README instructions on how to disable the TopBar, which is really helpful.

Would a PR be considered that would make it even easier -- for example a parameter in SwaggerUIBundle?

  // Build a system
  const ui = SwaggerUIBundle({
    ...
    presets: [
      SwaggerUIBundle.presets.apis,
      SwaggerUIStandalonePreset
    ],
    presets_config: {
       SwaggerUIStandalonePreset: {
           TopbarPlugin: false
       }
    }
    ...
  })

  window.ui = ui
}

There would be a new section called presets_config that would allow parameters to be passed for things like disabling the TopbarPlugin. This is just a rough idea, and I haven't really looked much at the swagger-ui codebase at all.

Here's the before vs after:

after:

swagger-ui version: commit 212396f

[webron]

Interesting thought, @tleyden. It might be useful to allow configuring which plugins are enabled via the main config, and maybe even extend it more at some point by adding the ability to configure specific plugins.

@shockey - your thoughts?

[roben]

This would also be nice to have for the schemes selection. Currently I am working around this by using a
<style> .swagger-ui .scheme-container, .swagger-ui .topbar { display: none !important; } </style>
block.

[shockey]

We can extend the plugin interface itself in order to make it easier to disable things, but I'm against adding flags for enabling/disabling specific things to the core- I'd rather those things happen through the plugin interface we have than add another layer of abstraction.

That being said, @ponelat wrote up up a way to disable entire plugins on the fly, though it would be a significant change to the plugin system as a whole: #3246. I think it would address this use case, and solve some other limitations we're facing as well.

[shockey]

Looking at this again, I may have misinterpreted the intent. I would be open to a namespace in the main configuration object that allows for options meant for a specific plugin.

We already have custom for this purpose (see #3108) formalizing it further would be nice.

My main concern is how to set defaults for config options. It's a handy feature that we use in the core configs for many things.

Off the top of my head, passing in defaults at plugin-register time (when the plugin passes in its components and Redux bits) would be a good option, though it increases the surface area of the plugin interface.

[ppKrauss]

Hi, the instructions at README, ".. remove Topbar plugin from presets..." (commenting // TopbarPlugin) are not working. There are a workaround?

---

PS#1: ideal is to remove the "false instruction" from README.

PS#2: see other motivations for "please remove the TopBar" at https://stackoverflow.com/q/44803881 ;-)

[tleyden]

@ppKrauss if it helps, I was able to get it to work. Check out: http://cecil-assets.s3-website-us-east-1.amazonaws.com/swagger/ and do "view source"

[ppKrauss]

Thanks @tleyden! With your clues I am building an "alternative swagger-ui" of pure HTML (and no TopbarPlugin) at https://github.com/okfn-brasil/swagger-ui-html