MCPcopy Index your code
hub / github.com/callstack/agent-device / handleFlingCommand

Function handleFlingCommand

src/core/dispatch-interactions.ts:714–743  ·  view source on GitHub ↗
(
  interactor: Interactor,
  positionals: string[],
)

Source from the content-addressed store, hash-verified

712}
713
714export async function handleFlingCommand(
715 interactor: Interactor,
716 positionals: string[],
717): Promise<Record<string, unknown>> {
718 const direction = parseGestureDirection(positionals[0], 'fling direction');
719 const x = Number(positionals[1]);
720 const y = Number(positionals[2]);
721 if (![x, y].every(Number.isFinite)) {
722 throw new AppError(
723 'INVALID_ARGS',
724 'gesture fling requires direction x y [distance] [durationMs]',
725 );
726 }
727 const distanceInput = positionals[3] ? Number(positionals[3]) : 180;
728 const distance = requireFinitePositiveNumber(distanceInput, 'distance');
729 const requestedDurationMs = positionals[4] ? Number(positionals[4]) : 50;
730 const durationMs = requireIntInRange(requestedDurationMs, 'durationMs', 16, 1_000);
731 const { x2, y2 } = pointOffsetByDirection(x, y, direction, distance);
732 await interactor.fling(x, y, x2, y2, durationMs);
733 return {
734 direction,
735 x,
736 y,
737 x2,
738 y2,
739 distance,
740 durationMs,
741 ...successText(`Flung ${direction}`),
742 };
743}
744
745export async function handleScrollCommand(
746 interactor: Interactor,

Callers 1

dispatch.tsFile · 0.90

Calls 6

requireIntInRangeFunction · 0.90
successTextFunction · 0.90
parseGestureDirectionFunction · 0.85
pointOffsetByDirectionFunction · 0.85
flingMethod · 0.80

Tested by

no test coverage detected

Used in the wild real call sites across dependent graphs

searching dependent graphs…