openObject: (
...args: [
subject: Unknown,
invoke: <I, O>(
op: Definition<I, O>,
...args: void extends I
? [input?: I, options?: InvokeOptions]
: [input: I, options?: InvokeOptions],
) => Effect<O, NoHandlerError>,
options: {
disposition?: "add" | "detail";
modifiers?: { shift?: boolean };
pivotId?: string;
},
],
) => Effect = ...
Type declaration
- (
...args: [
subject: Unknown,
invoke: <I, O>(
op: Definition<I, O>,
...args: void extends I
? [input?: I, options?: InvokeOptions]
: [input: I, options?: InvokeOptions],
) => Effect<O, NoHandlerError>,
options: {
disposition?: "add" | "detail";
modifiers?: { shift?: boolean };
pivotId?: string;
},
],
): Effect Parameters
- ...args: [
subject: Unknown,
invoke: <I, O>(
op: Definition<I, O>,
...args: void extends I
? [input?: I, options?: InvokeOptions]
: [input: I, options?: InvokeOptions],
) => Effect<O, NoHandlerError>,
options: {
disposition?: "add" | "detail";
modifiers?: { shift?: boolean };
pivotId?: string;
},
]
Returns Effect
Open an object from a card, beside the plank the card lives in. A card holds an object and has no idea where the nav tree shows it, so ask: NavigationOperation.ResolveNavigationTargets answers best-first, so an object's canonical home (its collection, a type section) wins over the generic database path. The space id has to come from the object's database — a bare
RefURI carries only an entity id, which would resolve against the active space and so mis-resolve a card showing an object from elsewhere.