Null-check call result rather than function itself

From the comment, it seems like this was supposed check for chords, rather than checking for the availability of `isChord`. Signed-off-by: Andrew Casey <[email protected]>
eclipse-theia · Apr 1, 2020 · 37def7c · 37def7c
1 parent 500432b
commit 37def7c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/examples/api-tests/src/monaco-api.spec.js b/examples/api-tests/src/monaco-api.spec.js
@@ -66,8 +66,7 @@ describe('Monaco API', async function () {
             }, {
                 label: 'Ctrl+Shift+Alt+K',
                 ariaLabel: 'Ctrl+Shift+Alt+K',
-                // eslint-disable-next-line no-null/no-null
-                electronAccelerator: null,
+                electronAccelerator: 'Ctrl+Shift+Alt+K',
                 userSettingsLabel: 'ctrl+shift+alt+K',
                 WYSIWYG: true,
                 chord: false,

diff --git a/packages/monaco/src/browser/monaco-resolved-keybinding.ts b/packages/monaco/src/browser/monaco-resolved-keybinding.ts
@@ -49,7 +49,7 @@ export class MonacoResolvedKeybinding extends monaco.keybindings.ResolvedKeybind
     }
 
     public getElectronAccelerator(): string | null {
-        if (this.isChord) {
+        if (this.isChord()) {
             // Electron cannot handle chords
             // eslint-disable-next-line no-null/no-null
             return null;