Selenium is going to remove client side validation of well-known Options
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 399
- Forks
- 185
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 13
Description
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Selenium pull request linked in the issue and compare its change with the Appium .NET client's handling of well-known Options. Identify the affected client-side validation entry points and existing tests before defining the compatibility work; done means the client continues to handle these Options correctly after Selenium removes that validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100