Join GitHub today
Specifying extension commands with no "name" #1170
In our efforts to integrate the WebDriver in the Permissions specification, we've identified a need that isn't addressed by the "protocol extension" mechanism today: defining a command that has no associated name.
In this case, we're looking to support setting a Permission in automation. We'd like to define a command for the HTTP POST method to the URI template
The definition of the "extension command prefix" defines its intent as: "separating extension commands from other commands in order to avoid potential resource conflicts with other implementations." Based on this definition,
We could circumvent this by defining the "prefix" as
I'd like to propose that the "extension command name" be made optional. Beyond documenting it as such, I believe the only other change to the WebDriver specification text would be in the instruction for how the "extension command URI Template" is constructed.
Would this be acceptable to the editors?