ASK: Client to accept capabilities as json
Open
Nobody has claimed this yet.
question
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 752
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 8
Description
Current, we need to explicitly provide the DesiredCaps, but server accepts the caps store in json format and will consider to start as per the values.
@TikhomirovSergey @SrinivasanTarget
Contributor guide
No contributing guide indexed for this repository
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 reviewing the Java client code that handles DesiredCaps and compare it with the server's JSON capability format described in the issue. Determine the relevant client entry point and test location before defining what accepting JSON should mean; done should be demonstrated by coverage for the requested capability input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100