Preferences
Use the Preferences API to make your extension configurable.
Preferences are configured in the manifest per command or shared in the context of an extension.
Required preferences need to be set by the user before a command opens. They are a great way to make sure that the user of your extension has everything set up properly.
API Reference
getPreferenceValues
A function to access the preference values that have been passed to the command.
Each preference name is mapped to its value, and the defined default values are used as fallback values.
Signature
Example
Return
An object with the preference names as property key and the typed value as property value.
Depending on the type of the preference, the type of its value will be different.
textfield
string
password
string
checkbox
boolean
dropdown
string
appPicker
file
string
directory
string
openExtensionPreferences
Opens the extension's preferences screen.
Signature
Example
Return
A Promise that resolves when the extensions preferences screen is opened.
openCommandPreferences
Opens the command's preferences screen.
Signature
Example
Return
A Promise that resolves when the command's preferences screen is opened.
Types
Preferences
A command receives the values of its preferences via the getPreferenceValues
function. It is an object with the preferences' name
as keys and their values as the property's values.
Depending on the type of the preference, the type of its value will be different.
textfield
string
password
string
checkbox
boolean
dropdown
string
appPicker
file
string
directory
string
Raycast provides a global TypeScript namespace called Preferences
which contains the types of the preferences of all the commands of the extension.
For example, if a command named show-todos
has some preferences, its getPreferenceValues
's return type can be specified with getPreferenceValues<Preferences.ShowTodos>()
. This will make sure that the types used in the command stay in sync with the manifest.
Last updated