[bidi][java][js] Add setFiles command of the Input Module

[pujagani]

User description

Thanks for contributing to Selenium!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

Add setFiles command of the Input Module as described in the BiDi spec https://w3c.github.io/webdriver-bidi/#command-input-setFiles

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

Type

enhancement

---

Description

• Added setFiles method overloads to the Input class in Java for setting files on input elements, along with tests.
• Implemented and tested the setFiles method in the JavaScript BiDi protocol implementation.
• Refactored ReferenceValue class in JavaScript to use private fields, enhancing encapsulation.

---

Changes walkthrough

	Relevant files
Enhancement	Input.java Add setFiles Method Overloads to Input Module                        java/src/org/openqa/selenium/bidi/module/Input.java Added setFiles method overloads to the Input class for setting files on input elements. One overload accepts a RemoteReference and a list of file paths, and the other accepts an element ID and a list of file paths. +21/-0    input.js Implement setFiles Method in Input Class for BiDi Protocol javascript/node/selenium-webdriver/bidi/input.js Implemented setFiles method in the Input class for setting files on input elements. Validates input types and constructs the appropriate command for the BiDi protocol. +25/-0    protocolValue.js Refactor ReferenceValue Class in BiDi Protocol Implementation javascript/node/selenium-webdriver/bidi/protocolValue.js Refactored ReferenceValue class to use private fields for handle and sharedId. Adjusted asMap method to work with the new private field structure. +11/-7
Tests	SetFilesCommandTest.java Test Coverage for setFiles Method in Input Module                java/test/org/openqa/selenium/bidi/input/SetFilesCommandTest.java Introduced tests for the newly added setFiles method in the Input module. Tests cover scenarios with both RemoteReference and element ID. +105/-0  setFiles_command_test.js Test Coverage for setFiles Method in BiDi Protocol              javascript/node/selenium-webdriver/test/bidi/setFiles_command_test.js Added tests for the setFiles method in the BiDi protocol implementation. Tests include scenarios for setting files using both a ReferenceValue and an element ID. +96/-0

---

✨ PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-pro]

PR Description updated to latest commit (8588306)

• Copy walkthrough table to "Files Changed" Tab

[codiumai-pr-agent-pro]

PR Review

(Review updated until commit 10b4dbb)

⏱️ Estimated effort to review [1-5]	3, because the PR introduces a new feature with multiple method overloads and corresponding tests in both Java and JavaScript. The complexity lies in understanding the BiDi protocol, the handling of file paths, and ensuring compatibility across different browsers and environments.
🧪 Relevant tests	Yes
🔍 Possible issues	Possible Bug: In the Java implementation, there's no validation to ensure that the files list is not empty before sending it to the bidi command. This could lead to unexpected behavior or errors if an empty list is passed.
	Possible Performance Issue: In the JavaScript implementation, the setFiles method constructs a new ReferenceValue object every time it's called, even when the element parameter is already a ReferenceValue. This could be optimized to avoid unnecessary object creation.
🔒 Security concerns	No

Code feedback:

---

relevant file	java/src/org/openqa/selenium/bidi/module/Input.java
suggestion	Consider adding a check to ensure that the files list is not empty in the setFiles methods. This can prevent sending commands that are guaranteed to fail and can provide a clearer error message to the user. [important]
relevant line	Map.of("context", browsingContext, "element", element.toJson(), "files", files)));

---

relevant file	javascript/node/selenium-webdriver/bidi/input.js
suggestion	Optimize the setFiles method to avoid creating a new ReferenceValue if the element parameter is already an instance of ReferenceValue. This can improve performance by reducing unnecessary object creation. [medium]
relevant line	? new ReferenceValue(RemoteReferenceType.SHARED_ID, element).asMap()

---

---

✨ Review tool usage guide:

---

Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:

/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:

[pr_reviewer]
some_config1=...
some_config2=...

Utilizing extra instructions The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize. Examples for extra instructions: [pr_reviewer] # /review # extra_instructions=""" In the 'possible issues' section, emphasize the following: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

How to enable\disable automation When you first install PR-Agent app, the default mode for the review tool is: pr_commands = ["/review", ...] meaning the review tool will run automatically on every PR, with the default configuration. Edit this field to enable/disable the tool, or to change the used configurations

Auto-labels The review tool can auto-generate two specific types of labels for a PR: a possible security issue label, that detects possible security issues (enable_review_labels_security flag) a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

Extra sub-tools The review tool provides a collection of possible feedbacks about a PR. It is recommended to review the possible options, and choose the ones relevant for your use case. Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example: require_score_review, require_soc2_ticket, require_can_be_split_review, and more.

Auto-approve PRs By invoking: /review auto_approve The tool will automatically approve the PR, and add a comment with the approval. To ensure safety, the auto-approval feature is disabled by default. To enable auto-approval, you need to actively set in a pre-defined configuration file the following: [pr_reviewer] enable_auto_approval = true (this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository) You can also enable auto-approval only if the PR meets certain requirements, such as that the estimated_review_effort is equal or below a certain threshold, by adjusting the flag: [pr_reviewer] maximal_review_effort = 5

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.

[codiumai-pr-agent-pro]

PR Code Suggestions

Category	Suggestions
Enhancement	Add exception handling for bidi.send method calls. Consider handling exceptions for the bidi.send method calls within setFiles methods. This will improve error handling and make the code more robust by allowing you to catch and handle specific exceptions that may occur during the execution of these methods. java/src/org/openqa/selenium/bidi/module/Input.java [93-96] -bidi.send( - new Command<>( - "input.setFiles", - Map.of("context", browsingContext, "element", element.toJson(), "files", files))); +try { + bidi.send( + new Command<>( + "input.setFiles", + Map.of("context", browsingContext, "element", element.toJson(), "files", files))); +} catch (Exception e) { + // Handle exception +}
	Add validation for handle and sharedId parameters in ReferenceValue constructor. Add validation to ensure that handle and sharedId are not both provided to the ReferenceValue constructor, as the current implementation allows setting both but only uses one based on the condition. This can lead to confusing behavior or bugs if both are mistakenly provided. javascript/node/selenium-webdriver/bidi/protocolValue.js [165-173] constructor(handle, sharedId) { + if (handle !== RemoteReferenceType.HANDLE && handle !== RemoteReferenceType.SHARED_ID) { + throw new Error("Invalid handle type provided."); + } if (handle === RemoteReferenceType.HANDLE) { - this.#handle = sharedId + this.#handle = sharedId; } else if (handle === RemoteReferenceType.SHARED_ID) { - this.#sharedId = sharedId - } else { - this.#handle = handle - this.#sharedId = sharedId + this.#sharedId = sharedId; } }
	Overload setFiles methods to accept a single file path. Consider overloading the setFiles method to also accept a single file path as a String instead of only a List. This would enhance usability for cases where only a single file needs to be set, making the API easier to use with less boilerplate code for the clients. java/src/org/openqa/selenium/bidi/module/Input.java [92-109] -public void setFiles(String browsingContext, RemoteReference element, List<String> files) { -public void setFiles(String browsingContext, String elementId, List<String> files) { +public void setFiles(String browsingContext, RemoteReference element, String file) { + setFiles(browsingContext, element, Collections.singletonList(file)); +} +public void setFiles(String browsingContext, String elementId, String file) { + setFiles(browsingContext, elementId, Collections.singletonList(file)); +}
Best practice	Remove or replace the console.log statement. Remove the console.log(response) statement or replace it with a more sophisticated logging mechanism. Directly logging to the console is generally not recommended in production code as it can clutter the output and leak potentially sensitive information. javascript/node/selenium-webdriver/bidi/input.js [83] -console.log(response) +// Consider using a logging library or framework for more control over logging
Possible issue	Enable skipped tests by replacing xit with it. Replace the xit function with it to enable the tests. The xit function is used to skip tests, which means these tests are currently not being executed. If the functionality is ready to be tested, using it will ensure the tests are run. javascript/node/selenium-webdriver/test/bidi/setFiles_command_test.js [52-73] -xit('can set files', async function () { -xit('can set files with element id', async function () { +it('can set files', async function () { +it('can set files with element id', async function () {

---

✨ Improve tool usage guide:

---

Overview:
The improve tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the improve tool (pr_code_suggestions section), use the following template:

/improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=...

With a configuration file, use the following template:

[pr_code_suggestions]
some_config1=...
some_config2=...

Enabling\disabling automation When you first install the app, the default mode for the improve tool is: pr_commands = ["/improve --pr_code_suggestions.summarize=true", ...] meaning the improve tool will run automatically on every PR, with summarization enabled. Delete this line to disable the tool from running automatically.

Utilizing extra instructions Extra instructions are very important for the improve tool, since they enable to guide the model to suggestions that are more relevant to the specific needs of the project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify relevant aspects that you want the model to focus on. Examples for extra instructions: [pr_code_suggestions] # /improve # extra_instructions=""" Emphasize the following aspects: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

A note on code suggestions quality While the current AI for code is getting better and better (GPT-4), it's not flawless. Not all the suggestions will be perfect, and a user should not accept all of them automatically. Suggestions are not meant to be simplistic. Instead, they aim to give deep feedback and raise questions, ideas and thoughts to the user, who can then use his judgment, experience, and understanding of the code base. Recommended to use the 'extra_instructions' field to guide the model to suggestions that are more relevant to the specific needs of the project, or use the custom suggestions 💎 tool With large PRs, best quality will be obtained by using 'improve --extended' mode.

More PR-Agent commands To invoke the PR-Agent, add a comment using one of the following commands: /review: Request a review of your Pull Request. /describe: Update the PR title and description based on the contents of the PR. /improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback. /ask <QUESTION>: Ask a question about the PR. /update_changelog: Update the changelog based on the PR's contents. /add_docs 💎: Generate docstring for new components introduced in the PR. /generate_labels 💎: Generate labels for the PR based on the PR's contents. /analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. See the tools guide for more details. To list the possible configuration parameters, add a /config comment.

See the improve usage page for a more comprehensive guide on using this tool.

[pujagani]

/review

[codiumai-pr-agent-pro]

Persistent review updated to latest commit 10b4dbb