From c5097ae4836174556aa9c21b0d603fd217fe0769 Mon Sep 17 00:00:00 2001 From: Kevin Sawicki Date: Tue, 20 Dec 2016 09:43:12 -0800 Subject: [PATCH] Add options to protocol.registerStandardSchemes docs --- docs/api/protocol.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/api/protocol.md b/docs/api/protocol.md index da5604b1fe7c..a7bf536ce625 100644 --- a/docs/api/protocol.md +++ b/docs/api/protocol.md @@ -28,9 +28,12 @@ of the `app` module gets emitted. The `protocol` module has the following methods: -### `protocol.registerStandardSchemes(schemes)` +### `protocol.registerStandardSchemes(schemes[, options])` * `schemes` String[] - Custom schemes to be registered as standard schemes. +* `options` Object (optional) + * `secure` Boolean (optional) - `true` to register the scheme as secure. + Default `false`. A standard scheme adheres to what RFC 3986 calls [generic URI syntax](https://tools.ietf.org/html/rfc3986#section-3). For example `http` and