81795744cf
* fix: ensure the typescript definitions only export correct value types In typescript there are two main types of "types" you can export, value types (class, const) and definition types (type, interface). The typescript compiler will let anything declared via const or class be used as a value. Unfortunately we were exporting a bunch of things (see the diff) as class/const when they weren't actually exported values. This lead to typescript being happy but the runtime throwing errors (not something we want). This change passes "exported-in" context through our docs, to the parser and then to the definitions generator to ensure we only mark things as exported in the ts defs that we actually export. Fixes #22167 * chore: update typescript-defs * chore: update typescript-defs * chore: fix bad typescript in IPC test * docs: test rendering of new syntax * chore: update per feedback, use same syntax but with 'this is not exportedd' line
1.1 KiB
1.1 KiB
Class: TouchBarPopover
Create a popover in the touch bar for native macOS applications
Process: Main
This class is not exported from the 'electron'
module. It is only available as a return value of other methods in the Electron API.
new TouchBarPopover(options)
options
Objectlabel
String (optional) - Popover button text.icon
NativeImage (optional) - Popover button icon.items
TouchBar - Items to display in the popover.showCloseButton
Boolean (optional) -true
to display a close button on the left of the popover,false
to not show it. Default istrue
.
Instance Properties
The following properties are available on instances of TouchBarPopover
:
touchBarPopover.label
A String
representing the popover's current button text. Changing this value immediately updates the
popover in the touch bar.
touchBarPopover.icon
A NativeImage
representing the popover's current button icon. Changing this value immediately updates the
popover in the touch bar.