Layouts are a special type of component that Swagger-UI uses as the root component for the entire application. You can define custom layouts in order to have high-level control over what ends up on the page.
+By default, Swagger-UI uses BaseLayout, which is built into the application. You can specify a different layout to be used by passing the layout's name as the layout parameter to Swagger-UI. Be sure to provide your custom layout as a component to Swagger-UI.
For example, if you wanted to create a custom layout that only displayed operations, you could define an OperationsLayout:
import React from "react"
+
+// Create the layout component
+class OperationsLayout extends React.Component {
+ render() {
+ const {
+ getComponent
+ } = this.props
+
+ const Operations = getComponent("Operations", true)
+
+ return {
+ <div>
+ <Operations />
+ </div>
+ }
+ }
+}
+
+// Create the plugin that provides our layout component
+const OperationsLayoutPlugin = function() {
+ return {
+ components: {
+ OperationsLayout: OperationsLayout
+ }
+ }
+}
+
+// Provide the plugin to Swagger-UI, and select OperationsLayout
+// as the layout for Swagger-UI
+SwaggerUI({
+ url: "http://petstore.swagger.io/v2/swagger.json",
+ plugins: [ OperationsLayoutPlugin ],
+ layout: "OperationsLayout"
+})
+If you'd like to build around the BaseLayout instead of replacing it, you can pull the BaseLayout into your custom layout and use it:
import React from "react"
+
+// Create the layout component
+class AugmentingLayout extends React.Component {
+ render() {
+ const {
+ getComponent
+ } = this.props
+
+ const BaseLayout = getComponent("BaseLayout", true)
+
+ return {
+ <div>
+ <div className="myCustomHeader">
+ <h1>I have a custom header above Swagger-UI!</h1>
+ </div>
+ <BaseLayout />
+ </div>
+ }
+ }
+}
+
+// Create the plugin that provides our layout component
+const AugmentingLayoutPlugin = function() {
+ return {
+ components: {
+ AugmentingLayout: AugmentingLayout
+ }
+ }
+}
+
+// Provide the plugin to Swagger-UI, and select AugmentingLayout
+// as the layout for Swagger-UI
+SwaggerUI({
+ url: "http://petstore.swagger.io/v2/swagger.json",
+ plugins: [ AugmentingLayoutPlugin ],
+ layout: "AugmentingLayout"
+})
+Swagger-UI leans heavily on concepts and patterns found in React and Redux.
If you aren't already familiar, here's some suggested reading:
In the following documentation, we won't take the time to define the fundamentals covered in the resources above.
++Note: Some of the examples in this section contain JSX, which is a syntax extension to JavaScript that is useful for writing React components.
+If you don't want to set up a build pipeline capable of translating JSX to JavaScript, take a look at React without JSX (reactjs.org).
+
The system is the heart of the Swagger-UI application. At runtime, it's a JavaScript object that holds many things:
getComponent is a helper function injected into every container component, which is used to get references to components provided by the plugin system.
All components should be loaded through getComponent, since it allows other plugins to modify the component. It is preferred over a conventional import statement.
Container components in Swagger-UI can be loaded by passing true as the second argument to getComponent, like so:
getComponent("ContainerComponentName", true)
+This will map the current system as props to the component.
@@ -377,7 +387,7 @@ - + @@ -388,7 +398,7 @@ diff --git a/docs/_book/customization/plugin-api.html b/docs/_book/customization/plugin-api.html index 98d07812..f5f3a874 100644 --- a/docs/_book/customization/plugin-api.html +++ b/docs/_book/customization/plugin-api.html @@ -192,7 +192,7 @@ - Creating a Custom Layout + Creating a custom layout @@ -349,7 +349,7 @@ statePlugins: { example: { actions: { - updateFavoriteColor: (str) => { + updateFavoriteColor: (obj) => { return { type: "EXAMPLE_SET_FAV_COLOR", payload: str @@ -361,16 +361,183 @@ } } +// elsewhere
+exampleActions.updateFavoriteColor({
+ name: "blue",
+ hex: "#0000ff"
+})
+The Action interface enables the creation of new Redux action creators within a piece of state in the Swagger-UI system.
This action creator function will be bound to the example reducer dispatcher and exposed to container components as exampleActions.updateFavoriteColor.
For more information about the concept of actions in Redux, see the Redux Actions documentation.
Reducers take a state (which is an Immutable map) and an action, and return a new state.
+Reducers must be provided to the system under the name of the action type that they handle, in this case, MYPLUGIN_UPDATE_SOMETHING.
const MyReducerPlugin = function(system) {
+ return {
+ statePlugins: {
+ example: {
+ reducers: {
+ "EXAMPLE_SET_FAV_COLOR": (state, action) => {
+ //
+ return state.set("favColor", fromJS(action.payload))
+ // we're updating the Immutable state object...
+ // we need to convert vanilla objects into an immutable type (fromJS)
+ // See immutable docs about how to modify the state
+ // PS: you're only working with the state under the namespace, in this case "example".
+ // So you can do what you want, without worrying about /other/ namespaces
+ }
+ }
+ }
+ }
+ }
+}
+Selectors take any number of functions as arguments, and passes all results to the last function.
+They're an easy way to keep logic for getting data out of state in one place, and is preferred over passing state data directly into components.
+See Reselect: createSelector for more information.
const MySelectorPlugin = function(system) {
+ return {
+ statePlugins: {
+ myPlugin: {
+ selectors: {
+ something: createSelector(
+ state => state.get("something") // return the whatever "something" points to
+ )
+ }
+ }
+ }
+ }
+}
+You can provide a map of components to be integrated into the system.
+Be mindful of the key names for the components you provide, as you'll need to use those names to refer to the components elsewhere.
+const MyComponentPlugin = function(system) {
+ return {
+ components: {
+ // components can just be functions
+ HelloWorld: () => <h1>Hello World!</h1>
+ }
+ }
+}
+// elsewhere
+const HelloWorld = getComponent("HelloWorld")
+Wrap Actions allow you to override the behavior of an action in the system.
+This interface is very useful for building custom behavior on top of builtin actions.
+A Wrap Action's first argument is oriAction, which is the action being wrapped. It is your responsibility to call the oriAction - if you don't, the original action will not fire!
const MySpecPlugin = function(system) {
+ return {
+ statePlugins: {
+ spec: {
+ actions: {
+ updateSpec: (str) => {
+ return {
+ type: "SPEC_UPDATE_SPEC",
+ payload: str
+ }
+ }
+ }
+ }
+ }
+ }
+}
+
+// this plugin allows you to watch changes to the spec that is in memory
+const MyWrapActionPlugin = function(system) {
+ return {
+ statePlugins: {
+ spec: {
+ wrapActions: {
+ updateSpec: function(oriAction, str) {
+ doSomethingWithSpecValue(str)
+ return oriAction(str) // don't forget!
+ }
+ }
+ }
+ }
+ }
+}
+Wrap Selectors allow you to override the behavior of a selector in the system.
+They are function factories with the signature (oriSelector, system) => (...args) => result.
This interface is useful for controlling what data flows into components. We use this in the core code to disable selectors based on the API definition's version.
+import { createSelector } from 'reselect'
+
+const MySpecPlugin = function(system) {
+ return {
+ statePlugins: {
+ spec: {
+ selectors: {
+ someData: createSelector(
+ state => state.get("something")
+ )
+ }
+ }
+ }
+ }
+}
+
+const MyWrapSelectorsPlugin = function(system) {
+ return {
+ statePlugins: {
+ spec: {
+ wrapSelectors: {
+ someData: (oriSelector, system) => (...args) => {
+ // you can do other things here...
+ // but let's just enable the default behavior
+ return oriSelector(...args)
+ }
+ }
+ }
+ }
+ }
+}
+Wrap Components allow you to override a component registered within the system.
+Wrap Components are function factories with the signature (OriginalComponent, system) => props => ReactElement.
const MyNumberDisplayPlugin = function(system) {
+ return {
+ components: {
+ NumberDisplay: ({ number }) => <span>{number}</span>
+ }
+ }
+}
+
+const MyWrapComponentPlugin = function(system) {
+ return {
+ wrapComponents: {
+ NumberDisplay: (Original, system) => (props) => {
+ if(props.number > 10) {
+ return <div>
+ <h3>Warning! Big number ahead.</h3>
+ </div>
+ } else {
+ return <Original {...props} />
+ }
+ }
+ }
+ }
+}
+The fn interface allows you to add helper functions to the system for use elsewhere.
+import leftPad from "left-pad"
+
+const MyFnPlugin = function(system) {
+ return {
+ fn: {
+ leftPad: leftPad
+ }
+ }
+}
+You can pull a pre-built docker image of the swagger-ui directly from Dockerhub:
+docker pull swaggerapi/swagger-ui
+docker run -p 80:8080 swaggerapi/swagger-ui
+Will start nginx with swagger-ui on port 80.
+Or you can provide your own swagger.json on your host
+docker run -p 80:8080 -e SWAGGER_JSON=/foo/swagger.json -v /bar:/foo swaggerapi/swagger-ui
+You can embed Swagger-UI's code directly in your HTML by using unkpg's interface:
+<script src="//unpkg.com/swagger-ui-dist@3/swagger-ui-bundle.js">See unpkg's main page for more information on how to use unpkg.
@@ -376,7 +385,7 @@ app.listen(3000) diff --git a/docs/_book/usage/version-detection.html b/docs/_book/usage/version-detection.html index c6f4bb23..6b6a5aed 100644 --- a/docs/_book/usage/version-detection.html +++ b/docs/_book/usage/version-detection.html @@ -192,7 +192,7 @@ - Creating a Custom Layout + Creating a custom layout diff --git a/docs/customization/custom-layout.md b/docs/customization/custom-layout.md index e69de29b..e3ab906b 100644 --- a/docs/customization/custom-layout.md +++ b/docs/customization/custom-layout.md @@ -0,0 +1,92 @@ +# Creating a custom layout + +**Layouts** are a special type of component that Swagger-UI uses as the root component for the entire application. You can define custom layouts in order to have high-level control over what ends up on the page. + +By default, Swagger-UI uses `BaseLayout`, which is built into the application. You can specify a different layout to be used by passing the layout's name as the `layout` parameter to Swagger-UI. Be sure to provide your custom layout as a component to Swagger-UI. + +