Open eglitise opened 9 months ago
for logs, we already re-use /se
endpoints to keep client's selenium client's compatibility so the appium
one is not necessary for logs
Good point, I was not aware of that. Then I guess there's only the session info endpoint left?
Yes, i think so.
Btw, I saw the /session/<session id>
endpoint was proposed once in the past in the w3c in https://github.com/w3c/webdriver
I don't recall right now about the details but the propose was closed after some discussion.
Based on #19851. These are just ideas and the exact endpoint values are open to discussion.
GET /session/:sessionId
=>GET /session/:sessionId/appium/info
(already exists in Selenium asGET /session/:sessionId/log
=>GET /session/:sessionId/appium/log
/se/log
)(already exists in Selenium asGET /session/:sessionId/log/types
=>GET /session/:sessionId/appium/appium/types
/se/log/types
)