Skip to content

Latest commit

 

History

History
172 lines (114 loc) · 5.83 KB

File metadata and controls

172 lines (114 loc) · 5.83 KB

Raycast Cross-Extension Conventions

Defines the development approach for cross-extension in Raycast

raycast-cross-extension-badge

Background

Raycast has tons of extensions so far. But most of them are standalone, it’s hard to use their ability from other extensions.

Install

npm i raycast-cross-extension

Usages

Consumer Usage

Add your target extension handle to the crossExtensions list of package.json. This field allows providers to get to know who is using their extension. See maintenance.

{
	"crossExtensions": ["target-extensions-author-name/target-extension-name"]
}

We recommend always using the crossLaunchCommand() API to launch cross-extensions even your extension doesn't use the callback launch feature.

You may need to catch exceptions from crossLaunchCommand() if the target command is not installed. The open() redirects to the Store when crossLaunchCommand() errored.

Example

import { LaunchType, open } from "@raycast/api";
import { crossLaunchCommand } from "raycast-cross-extension";

crossLaunchCommand({
	name: "target-command-name",
	type: LaunchType.UserInitiated,
	extensionName: "target-extension-name",
	ownerOrAuthorName: "target-extension-author-name",
	context: {
		foo: "foo",
		bar: "bar",
	},
}).catch(() => {
	open(
		"raycast://extensions/target-extension-author-name/target-extension-name",
	);
});

Provider Usage

Incoming parameters can be received from LaunchContext.

The callbackLaunchOptions is used for running the callback launchCommand() to the source extension.

Please note passing parameters through Arguments is not recommneded since it supports string only.

But a command with arguments is still useful if you want to reuse your existing arguments-based commands as the cross-extension entrance. For exmaple, the Say extension is using the typeToSay arguments-based command for receiving cross-extension parameters.

Example

import { LaunchProps } from "@raycast/api";
import { callbackLaunchCommand, LaunchOptions } from "raycast-cross-extension";

type LaunchContext = {
	foo?: string;
	bar?: string;
	callbackLaunchOptions?: LaunchOptions;
};

export default function Command({
	launchContext = {},
}: LaunchProps<{ launchContext?: LaunchContext }>) {
	const { foo, bar, callbackLaunchOptions } = launchContext;
	// ...
	callbackLaunchCommand(callbackLaunchOptions, {
		result: "hello, world",
	});
}

API

crossLaunchCommand(options, callbackOptions?)

options

Type: LaunchOptions

Options for launch the target command.

callbackOptions

Type: Partial<LaunchOptions> | false

Optional. Options for launch the callback command. It will be used in the callback stage with default values below:

  • name defaults to environment.commandName
  • extensionName defaults to environment.extensionName
  • ownerOrAuthorName defaults to environment.ownerOrAuthorName or the field in package.json
  • type defaults to LaunchType.UserInitiated

You can set it to false to disable command callback.

callbackLaunchCommand(options, payload?)

options

Type: LaunchOptions

Pass in launchContext.callbackLaunchOptions. This is used to load options for callback.

payload

Type: LaunchOptions['context']

Optional. Context data for sending back to consumer command.

Maintenance

When you make breaking changes, keep an eye out for other projects using your API.

You can search for your extension handle your-author-name/your-extension-name from the raycast/extensions to find that extension using your extension.

Badges

Show the world your extension implemented Cross-Extension.

raycast-cross-extension-badge

[![](https://shields.io/badge/Raycast-Cross--Extension-eee?labelColor=FF6363&logo=raycast&logoColor=fff&style=flat-square)](https://github.com/LitoMore/raycast-cross-extension-conventions)

Who's using Cross-Extension

Consumers

Providers

Utilities

License

CC0-1.0