Move Sobek option parsing to the mapping layer

[inancgumus]

What

• Move Sobek option parsing to the mapping layer.

Why

• Separation of concerns.
• Option parsing is only required by the mapping layer.
• To simplify and make the code and tests easy to reason about.

Current options to move

• Move ConvertSelectOptionValues from browser to common #5302
• ElementHandleBaseOptions
• Frame options
• Locator options
• Mouse options
• Size.Parse
• PageEmulateMediaOptions
• PageReloadOptions
• PageScreenshotOptions

Example

• In this code, the parsing happens in the mapping layer.

Related

• This issue is a continuation of the epic issue Move Sobek entirely out of the business logic #4219.

[anupriyakkumari]

Hi, I would like to take this issue up. Thanks.

[joanlopez]

Hi, I would like to take this issue up. Thanks.

Great, thanks for letting us know!

Let me invoke @inancgumus, and see what's his take here, as he's the one with the largest context/current status acknowledge. How good fit do you see this issue for community contributions? Have we made any progress so far? Anyone's working on it already? 🤔

[inancgumus]

@anupriyakkumari I've updated the list. You can work on the next ones. Please send a PR for the next one (please do not send all of them in a single PR), and we can discuss how to move forward from there. Thanks a lot for your interest in contributing!

@joanlopez, it's a great issue to make a first contribution.