From 5478cc7e8e1530b075fc2988fe0de30e063536a9 Mon Sep 17 00:00:00 2001 From: Robo Date: Wed, 13 Feb 2019 00:19:47 +0530 Subject: [PATCH] chore: fix lint errors (#16906) --- docs/api/protocol.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/api/protocol.md b/docs/api/protocol.md index 84b43094b0a1..d9804a87d9c1 100644 --- a/docs/api/protocol.md +++ b/docs/api/protocol.md @@ -76,18 +76,21 @@ are disabled for non standard schemes. So in general if you want to register a custom protocol to replace the `http` protocol, you have to register it as a standard scheme. `protocol.registerSchemesAsPriviliged` can be used to replicate the functionality of the previous `protocol.registerStandardSchemes`, `webFrame.registerURLSchemeAs*` and `protocol.registerServiceWorkerSchemes` functions that existed prior to Electron 5.0.0, for example: -``` -# before (<= v4.x) + +**before (<= v4.x)** +```javascript // Main protocol.registerStandardSchemes(['scheme1', 'scheme2'], { secure: true }) // Renderer webFrame.registerURLSchemeAsPrivileged('scheme1', { secure: true }) webFrame.registerURLSchemeAsPrivileged('scheme2', { secure: true }) +``` -# after (>= v5.x) +**after (>= v5.x)** +```javascript protocol.registerSchemesAsPriviliged([ { scheme: 'scheme1', privileges: { standard: true, secure: true } }, - { scheme: 'scheme2', privileges: { standard: true, secure: true } }, + { scheme: 'scheme2', privileges: { standard: true, secure: true } } ]) ```