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
22 lines
942 B
Markdown
22 lines
942 B
Markdown
## Class: TouchBarSpacer
|
|
|
|
> Create a spacer between two items in the touch bar for native macOS applications
|
|
|
|
Process: [Main](../glossary.md#main-process)<br />
|
|
_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 TouchBarSpacer(options)`
|
|
|
|
* `options` Object
|
|
* `size` String (optional) - Size of spacer, possible values are:
|
|
* `small` - Small space between items. Maps to `NSTouchBarItemIdentifierFixedSpaceSmall`. This is the default.
|
|
* `large` - Large space between items. Maps to `NSTouchBarItemIdentifierFixedSpaceLarge`.
|
|
* `flexible` - Take up all available space. Maps to `NSTouchBarItemIdentifierFlexibleSpace`.
|
|
|
|
### Instance Properties
|
|
|
|
The following properties are available on instances of `TouchBarSpacer`:
|
|
|
|
#### `touchBarSpacer.size`
|
|
|
|
A `String` representing the size of the spacer. Can be `small`, `large` or `flexible`.
|