Appium 2.0 - appium-gestures-plugin - support for .net core #60
Description
Hi Team,
We have framework built on .net core with appium 2.0 and I would want to use the plugins available.
Currently we are using appium-wait-plugin and removed the explicit waits within the scripts.
eg:
wait-plugin] Element with name strategy for Passcode field selector found.
[wait-plugin] Check if element is displayed
[debug] [XCUITestDriver@1040 (d327d853)] Matched ‘/element/04000000-0000-0000-A747-010000000000/displayed’ to command name ‘elementDisplayed’
[debug] [XCUITestDriver@1040 (d327d853)] Proxying [GET /element/04000000-0000-0000-A747-010000000000/displayed] to [GET http://127.0.0.1:8100/session/14ACBB8C-5909-4297-89AE-0120E197DFA8/element/04000000-0000-0000-A747-010000000000/displayed] with no body
⠏ Waiting to find element with name strategy for Passcode field selector[debug] [XCUITestDriver@1040 (d327d853)] Got response with status 200: {“value”:true,“sessionId”:“14ACBB8C-5909-4297-89AE-0120E197DFA8”}
[wait-plugin] Element is displayed!
:heavy_tick: Waiting to find element with name strategy for Passcode field selector
[AppiumDriver@75c5] Executing default handling behavior for command ‘findElement’
My Questions, Would this be same for gestures, as I see a different implementation under
WDIO
driver.addCommand(
'dragAndDrop',
command('POST', '/session/:sessionId/plugin/actions/dragAndDrop', {
command: 'dragAndDrop',
parameters: [
{
name: 'sourceId',
type: 'string',
description: 'a valid parameter',
required: true,
},
{
name: 'destinationId',
type: 'string',
description: 'a valid parameter',
required: true,
},
],
})
);
await driver.dragAndDrop(sourceId, destinationId);