Filters
Filters enable easily modifying data that is passed around in Local. Much like WordPress' filters, all filters in Local must return a value.
Filter Name
Description
Allows you to add or modify items in the main app menu (top bar menu)
Callback Function Parameters
- macOS Menu Template
- Current Platform provided by
process.platform
function(menu: MenuTemplate[], platform: string): MenuTemplate[];
_____________________________________________________________
Filter Name
Description
Allows you to add menu items to the Site Info More menu inside of a single site view.
Callback Function Parameters
- menuItems
function(menuItems: SiteInfoMoreMenuItem[], site: Site): SiteInfoMoreMenuItem[];
Example
hooks.addFilter('siteInfoMoreMenu', function (menu, site) {
menu.push({
label: 'Volumes',
enabled: !this.context.router.isActive(`/site-info/${site.id}/volumes`),
click: () => {
context.events.send('goToRoute', `/site-info/${site.id}/volumes`);
},
});
return menu;
});
_____________________________________________________________
Filter Name
Description
Add-ons have the ability to add items to Local's preferences section by using the
preferencesMenuItems filter hook. This filter will add a new item to the left hand column of all Preferences views and allow add-ons to add their own content section.
An
AddonSettingsItem object is given to Local via the preferencesMenuItems hook (see usage examples below). This can then render an array of PreferencesSection's or any React component. The latter is provided mainly as an escape hatch in the case that an add-on needs more flexibility. Each PreferencesSection then provides an optional header and a single or array of MenuContentRowItem(s).Props passed to<Row />or<Override />components
{
// React Router props (types are not accurately documented here and developers should reference the React Router documentation for more details)
history: any;
location: any;
match: any;
params: any;
// controls whether or not the "apply" button (rendered by Local) is enabled (clickable) or disabled (not clickable)
setApplyButtonDisabled: (isDisabled: boolean) => void;
// various other props may be passed via Local but are not an offically supported component of this API as of the time of writing
}
Callback Function Parameters
- preferencesMenu
function(preferencesItem: PreferencesItem[]): PreferencesItem[];
Examples
"Standard" example passing in sections and sub-headers
const preferenceItem: AddonSettingsItem = {
path: 'image-optimizer',
displayName: 'Image Optimizer',
sections: [
{
// subHeader is optional and if omitted, no subHeader will be rendered
subHeader: 'header 1',
rows: [
{
// this defines what string will be rendered in the left hand "column" of a row
name: 'line 1',
// this defines what will be rendered in the right hand "column" of a row. It can be any React component.
component: Preferences,
},
// ...add some more rows if you want
],
},
// ...add some more sections if you want
],
onApply: () => {
console.log('changes applied!')
},
componentProps: {
// This optional object can be any arbitrary props to get passed to your row components (or Override component)
},
};
hooks.addFilter(
'preferencesMenuItems',
(menu) => {
menu.push(preferenceItem);
// remember to return the menu array here! If you don't Local won't be able to render your Preference item
return menu;
}
);
Overriding Sections with a single React Component (allows you to render arbitrary things in the "content area")
const preferenceItem = {
path: 'image-optimizer',
displayName: 'Image Optimizer',
// this can also just be any old React component. It will be rendered in the Preferences content area
sections: (props) => <div>{props.title}<div/>,
onApply: () => {
console.log('changes applied!')
},
componentProps: {
/* Arbitrary props that will get passed to your row components or section override component. */
/* here we are passing it "title" which will get passed to the "sections" component */
title: 'Preferences Title',
},
}
hooks.addFilter(
'preferencesMenuItems',
(menu) => {
menu.push(preferenceItem);
return menu;
};
);
ENV_ID and ENV_VERSION are for illustrative purposes only and should be replaced with a static value or variable.Filter Name | Parameters |
importBlueprintSiteSettings:ENV_ID:ENV_VERSION |
Last modified 2yr ago