Initial keyboard shortcuts configuration implementation #496

Merged
franknoirot merged 11 commits from keyboard-shortcuts into main 2021-09-10 00:12:59 +02:00
4 changed files with 107 additions and 89 deletions
Showing only changes of commit 9887eb4804 - Show all commits

View File

@@ -21,7 +21,7 @@ const AllShortcutsModal = () => {
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this
<Dialog open={open} onClose={() => setOpen(false)} className={classes.root}>
<div className="bg-ch-gray-700 font-fira-sans max-w-7xl rounded shadow-lg text-ch-gray-300 p-4">
<h2 className="text-2xl mb-4">All Shortcuts</h2>
{ editorMenuConfig.map(menu => menu.items.length ? (
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this
{ editorMenuConfig.filter(menu => menu.items.length).map(menu =>
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this
<section key={"allshortcuts-"+menu.name}
className="my-6">
Irev-Dev commented 2021-09-08 09:53:33 +02:00 (Migrated from github.com)
Review

Seems to be a weird artifact on the rounded corner, not sure if worth fixing?
image

Seems to be a weird artifact on the rounded corner, not sure if worth fixing? ![image](https://user-images.githubusercontent.com/29681384/132469191-d50fe9aa-dfed-43ca-8cbc-b83a198182e3.png)
franknoirot commented 2021-09-08 15:27:02 +02:00 (Migrated from github.com)
Review

Oh yeah lemme check it out, I bet it's a difference between the Modal and the inner content, and maybe I rounded the inner stuff as well and they're basically overlapping.

Oh yeah lemme check it out, I bet it's a difference between the Modal and the inner content, and maybe I rounded the inner stuff as well and they're basically overlapping.
<h3 className="text-xl border-b-2 pb-2 mb-2">{ menu.label }</h3>
@@ -32,7 +32,7 @@ const AllShortcutsModal = () => {
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this
</div>
))}
</section>
) : <></>)}
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this
)}
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this
</div>
</Dialog>
)
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
Irev-Dev commented 2021-09-08 10:00:35 +02:00 (Migrated from github.com)
Review

Should this also have a button in the menu, how will users learn how to get this modal up?

Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused.

Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.

Should this also have a button in the menu, how will users learn how to get this modal up? Why did you choose this combo, is this a pattern elsewhere? I'm concerned that is the same hotkey as commenting a line in the editor, since the editor is currently swallowing this hotkey so it still works in the editor but seems weird having two different behaviour depending on where you're focused. Maybe it's a mac only thing, but similar to the above cmd alt R only resets the viewer when I'm not focused on the edit, because its already a hotkey in the editor. Seems like we're going to be competing for hotkeys from the monaco editor.
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:38:07 +02:00 (Migrated from github.com)
Review

Ah crap this is all good consideration @Irev-Dev.

Here are my recommendations for these 2:

  • All Shortcuts:command+/ 👉🏻 ctrl+shift+?. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View?
  • Reset Layout: command+alt+R 👉🏻 ctrl+shift+R. It appears that ctrl+shift is a fairly reliable key combination.

Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?

Ah crap this is all good consideration @Irev-Dev. Here are my recommendations for these 2: - **All Shortcuts**:`command+/` 👉🏻 `ctrl+shift+?`. This is what Figma's shortcut to show shortcuts is. I agree this should have a button in the menu. Would it go under View? - **Reset Layout**: `command+alt+R` 👉🏻 `ctrl+shift+R`. It appears that `ctrl+shift` is a fairly reliable key combination. Separately, should we have a part of this component or its tests have a list of the Monaco shortcuts to verify any new ones aren't stepping on them?
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
franknoirot commented 2021-09-08 15:53:44 +02:00 (Migrated from github.com)
Review

One thing that's weird to me is that HotKeys treats Ctrl and Cmd as the Windows/Mac alternatives, but it's really Cmd and Win keys that are analogous, usually called the OS key within the browser, and Ctrl is a key that both OSes have.

One thing that's weird to me is that HotKeys treats `Ctrl` and `Cmd` as the Windows/Mac alternatives, but it's really `Cmd` and `Win` keys that are analogous, usually called the OS key within the browser, and `Ctrl` is a key that both OSes have.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
Irev-Dev commented 2021-09-09 10:54:34 +02:00 (Migrated from github.com)
Review
  • ctrl shift ? I think make sense for the modal :)
  • test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves.
  • I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
- ctrl shift ? I think make sense for the modal :) - test might be good, but not sure if there is a way it pull hotkeys out of monaco without hardcoding them ourselves. - I think the library does that for practical reasons since ctrl is the most common key used for hotkey for win and cmd is the most common for mac, for example cmd c, cmd v is copy paste.
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
franknoirot commented 2021-09-09 16:23:00 +02:00 (Migrated from github.com)
Review

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find this GH issue comment about it. There doesn't appear to be like KeybindingsRegistry.getAll() method or anything like that.

The Monaca online editor is built on top of Monaco and has this hardcoded list of shortcuts that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And this issue has been raised in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really.

Want me to open an issue for the tests? I feel like we can do that a bit later, right?

Yeah doesn't appear to be a great way to pull them out programmatically, only was able to find [this GH issue comment about it](https://github.com/microsoft/monaco-editor/issues/823#issuecomment-470754000). There doesn't appear to be like `KeybindingsRegistry.getAll()` method or anything like that. The Monaca online editor is built on top of Monaco and has this hardcoded [list of shortcuts](https://docs.monaca.io/en/products_guide/monaca_ide/editor/) that we could pull from for a hardcoded solution. I think they'll be pretty stable so that might not be too bad? And [this issue has been raised](https://github.com/microsoft/monaco-editor/issues/102) in Monaco for an easy API for swapping out keyboard shortcuts, I couldn't find a clean holistic API for keybindings at all really. Want me to open an issue for the tests? I feel like we can do that a bit later, right?
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
Irev-Dev commented 2021-09-09 21:20:29 +02:00 (Migrated from github.com)
Review

Yeah sure, sounds good.

Yeah sure, sounds good.
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this
franknoirot commented 2021-09-10 00:12:40 +02:00 (Migrated from github.com)
Review

Added issue #499 to track this

Added issue #499 to track this

View File

@@ -0,0 +1,49 @@
import { Menu } from '@headlessui/react'
import { useHotkeys } from 'react-hotkeys-hook';
export function DropdownItem({ config, state, thunkDispatch }) {
console.log({ name: config.label, shortcut: config.shortcut, callback: handleClick})
useHotkeys(config.shortcut, handleClick)
function handleClick(e) {
console.log(e, config)
e.preventDefault()
config.callback(e, {state, thunkDispatch})
}
return (
<Menu.Item>
{({ active }) => (
<button
className={`${active && 'bg-gray-600'} px-2 py-1 text-left`}
onClick={handleClick}
>
{config.label}
{config.shortcutLabel && <span className="text-gray-400 pl-4">{ config.shortcutLabel }</span> }
</button>
)}
</Menu.Item>
)
}
export function Dropdown({
label,
disabled,
children,
}: {
label: string,
disabled: boolean,
children: React.ReactNode,
}) {
return (
<div className="relative">
<Menu>
<Menu.Button className={"text-gray-100" + (disabled ? " text-gray-400 cursor-not-allowed" : "")} disabled={disabled}>{label}</Menu.Button>
{ children &&
<Menu.Items className="absolute flex flex-col mt-4 bg-ch-gray-760 rounded text-gray-100 overflow-hidden whitespace-nowrap border border-ch-gray-700">
{children}
</Menu.Items>
}
</Menu>
</div>
)
}

View File

@@ -1,31 +1,12 @@
import { Menu } from '@headlessui/react'
import { useHotkeys } from 'react-hotkeys-hook';
import { useIdeContext } from 'src/helpers/hooks/useIdeContext'
import Svg from 'src/components/Svg/Svg'
import { useRender } from 'src/components/IdeWrapper/useRender'
import { makeStlDownloadHandler, PullTitleFromFirstLine } from './helpers'
import { useSaveCode } from 'src/components/IdeWrapper/useSaveCode'
import CadPackage from 'src/components/CadPackage/CadPackage'
import { EditorMenuConfig, EditorMenuItemConfig, editorMenuConfig } from './menuConfig'
import { editorMenuConfig } from './menuConfig'
import AllShortcutsModal from './AllShortcutsModal'
import { Dropdown } from './Dropdowns';
const EditorMenu = () => {
const handleRender = useRender()
const saveCode = useSaveCode()
const { state, thunkDispatch } = useIdeContext()
const handleStlDownload = makeStlDownloadHandler({
type: state.objectData?.type,
ideType: state.ideType,
geometry: state.objectData?.data,
quality: state.objectData?.quality,
fileName: PullTitleFromFirstLine(state.code || ''),
thunkDispatch,
})
editorMenuConfig.forEach(menu =>
menu.items.forEach(({shortcut, callback}) =>
useHotkeys(shortcut, callback), [state])
)
return (<>
<div className="flex justify-between bg-ch-gray-760 text-gray-100">
@@ -36,8 +17,12 @@ const EditorMenu = () => {
<div className="grid grid-flow-col-dense gap-6 px-5">
{ editorMenuConfig.map(menu => (
<Dropdown label={menu.label} disabled={menu.disabled} key={menu.label +"-dropdown"}>
{ menu.items.map(itemConfig => (
<DropdownItem config={itemConfig} key={ menu.label +"-"+ itemConfig.label} />)
{ menu.items.map(itemConfig =>
<itemConfig.component
state={state}
thunkDispatch={thunkDispatch}
config={itemConfig}
key={menu.label +"-"+ itemConfig.label } />
) }
</Dropdown>
)) }
@@ -56,43 +41,4 @@ const EditorMenu = () => {
</>)
}
export default EditorMenu
function DropdownItem({ config }) {
return (
<Menu.Item>
{({ active }) => (
<button
className={`${active && 'bg-gray-600'} px-2 py-1 text-left`}
onClick={config.callback}
>
{config.label}
{config.shortcutLabel && <span className="text-gray-400 pl-4">{ config.shortcutLabel }</span> }
</button>
)}
</Menu.Item>
)
}
function Dropdown({
label,
disabled,
children,
}: {
label: string,
disabled: boolean,
children: React.ReactNode,
}) {
return (
<div className="relative">
<Menu>
<Menu.Button className={"text-gray-100" + (disabled ? " text-gray-400 cursor-not-allowed" : "")} disabled={disabled}>{label}</Menu.Button>
{ children &&
<Menu.Items className="absolute flex flex-col mt-4 bg-ch-gray-760 rounded text-gray-100 overflow-hidden whitespace-nowrap border border-ch-gray-700">
{children}
</Menu.Items>
}
</Menu>
</div>
)
}
export default EditorMenu

View File

@@ -1,10 +1,12 @@
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
import React from 'react'
import { useIdeContext } from 'src/helpers/hooks/useIdeContext'
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
import { useRender } from 'src/components/IdeWrapper/useRender'
import { makeStlDownloadHandler, PullTitleFromFirstLine } from './helpers'
import { useSaveCode } from 'src/components/IdeWrapper/useSaveCode'
franknoirot commented 2021-09-08 16:39:40 +02:00 (Migrated from github.com)
Review

This won't work currently because I backed out of writing it, but @Irev-Dev should I use a React Context to make the AllShortcutsModal able to be opened from outside of the component? I could make its own little context to provide around the IdeWrapper component, or the page component itself. I might try that and see if you like it.

This won't work currently because I backed out of writing it, but @Irev-Dev should I use a React Context to make the `AllShortcutsModal` able to be opened from outside of the component? I could make its own little context to provide around the `IdeWrapper` component, or the page component itself. I might try that and see if you like it.
franknoirot commented 2021-09-08 17:39:09 +02:00 (Migrated from github.com)
Review

Tried this approach below.

Tried this approach below.
import Svg from 'src/components/Svg/Svg'
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
import { DropdownItem } from './Dropdowns'
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
export function cmdOrCtrl() {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
return /(Mac|iPhone|iPod|iPad)/i.test(navigator.platform) ? '⌘' : 'Ctrl'
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
}
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
const fileMenuConfig = {
name: 'file',
@@ -14,30 +16,51 @@ const fileMenuConfig = {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
{
label: 'Save & Render',
shortcut: 'ctrl+s, command+s',
shortcutLabel: <><CmdOrCtrl/> S</>,
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
// This is my main issue. How do I pass in a callback that relies on the hooks and state within the component?
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
// Put another way, how do I make the state and hooks used within a component configurable from outside the component itself?
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
callback: (e, /* { options } */) => {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
// These do not work
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
// const handleRender = useRender()
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
// const saveCode = useSaveCode()
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
// handleRender()
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
// saveCode({ code: state.code })
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
e.preventDefault()
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
alert('Saving & Rendering!')
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
shortcutLabel: cmdOrCtrl() + ' S',
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
component: (props) => {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
const { state, config } = props
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
const handleRender = useRender()
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
const saveCode = useSaveCode()
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
function onRender(e) {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
e.preventDefault()
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
handleRender()
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
saveCode({ code: state.code })
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
}
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
config.callback = onRender
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
return <DropdownItem {...props} />
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
},
},
{
label: 'Download STL',
shortcut: 'ctrl+shift+d, command+shift+d',
shortcutLabel: <><CmdOrCtrl/> Shift D</>,
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
callback: () => alert('Downloading STL!'),
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
shortcutLabel: cmdOrCtrl() + ' Shift D',
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
component: (props) => {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
const { state, thunkDispatch, config } = props
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
const handleStlDownload = makeStlDownloadHandler({
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
type: state.objectData?.type,
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
ideType: state.ideType,
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
geometry: state.objectData?.data,
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
quality: state.objectData?.quality,
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
fileName: PullTitleFromFirstLine(state.code || ''),
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
thunkDispatch,
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
})
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
config.callback = handleStlDownload
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
return <DropdownItem {...props} />
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
}
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
},
{
label: 'Cook Donut',
shortcut: 'ctrl+d, command+d',
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
shortcutLabel: <><CmdOrCtrl/> D</>,
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
callback: () => alert('Donut is cooked!'),
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
shortcut: 'ctrl+os+d',
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
shortcutLabel: cmdOrCtrl() + ' D',
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
component: (props) => {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
const { config } = props
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
config.callback = () => alert('Donut is cooked!')
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
return <DropdownItem {...props} />
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
}
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
}
]
}
@@ -57,8 +80,12 @@ const viewMenuConfig = {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
{
label: 'Reset layout',
shortcut: 'ctrl+alt+r, command+alt+r',
shortcutLabel: <><CmdOrCtrl/> Alt R</>,
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
callback: () => alert('Resetting the layout!'),
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
shortcutLabel: cmdOrCtrl() + ' Alt R',
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
component: (props) => {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
const { config, thunkDispatch } = props
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
config.callback = () => thunkDispatch({ type: 'resetLayout' })
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
return <DropdownItem {...props } />
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
}
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
},
],
}
@@ -82,8 +109,4 @@ export interface EditorMenuConfig {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
label: string,
disabled: boolean,
items: Array<EditorMenuItemConfig>,
}
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
function CmdOrCtrl() {
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
return <span> { /(Mac|iPhone|iPod|iPad)/i.test(navigator.platform) ? '⌘' : 'Ctrl' }</span>
Irev-Dev commented 2021-09-08 10:35:59 +02:00 (Migrated from github.com)
Review

if you make this:

const fileMenuConfig: EditorMenuConfig = {

Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since component doesn't exist on EditorMenuItemConfig.

if you make this: ```suggestion const fileMenuConfig: EditorMenuConfig = { ``` Thdn the linter (assuming you've got ts setup with your editor) should tell you if your obeying your own types for this menu, and I think you're not since `component` doesn't exist on `EditorMenuItemConfig`.
Irev-Dev commented 2021-09-08 10:38:23 +02:00 (Migrated from github.com)
Review

I think callback is not needed now and component is?

I think callback is not needed now and component is?
franknoirot commented 2021-09-08 16:00:31 +02:00 (Migrated from github.com)
Review

Yup it yelled at me now!

Yup it yelled at me now!
}