You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Remove TOML warning for the upcoming TOML parser change in #14470
Motivation and Context
Remove warning because as said We can add a warning with the current code base about the upcoming change, and maybe merge this PR after 2 versions so the end users get a chance to update the TOML. as said in #14470 (comment)
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)
Implement custom validation for unquoted strings to maintain previous warning functionality
Consider adding a custom validation method to check for unquoted strings in the TOML content, to maintain the previous warning functionality without using a logger.
public TomlConfig(Reader reader) {
try {
toml = JToml.parse(reader);
+ validateQuotedStrings(reader);
} catch (IOException e) {
throw new ConfigException("Unable to read TOML.", e);
} catch (ParseException e) {
throw new ConfigException(
Apply this suggestion
Suggestion importance[1-10]: 7
Why: This suggestion provides a more proactive approach to maintaining the functionality of the removed warning. Implementing custom validation for unquoted strings helps ensure code quality and prepares for future TOML parser changes, making it a valuable enhancement.
7
Maintainability
Add a reminder for future TOML parser changes to maintain awareness of potential issues
Consider adding a deprecation notice or TODO comment to remind developers about the upcoming change in TOML parser behavior regarding unquoted strings.
public TomlConfig(Reader reader) {
try {
toml = JToml.parse(reader);
+ // TODO: Add validation for unquoted strings once new TOML parser is implemented
} catch (IOException e) {
throw new ConfigException("Unable to read TOML.", e);
} catch (ParseException e) {
throw new ConfigException(
Apply this suggestion
Suggestion importance[1-10]: 5
Why: The suggestion is relevant as it addresses the removed warning about future TOML parser changes. Adding a TODO comment maintains awareness of the issue without using the removed logger, which is moderately useful for future maintenance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Remove TOML warning for the upcoming TOML parser change in #14470
Motivation and Context
Remove warning because as said
We can add a warning with the current code base about the upcoming change, and maybe merge this PR after 2 versions so the end users get a chance to update the TOML.as said in #14470 (comment)Types of changes
Checklist
PR Type
Bug fix
Description
Changes walkthrough 📝
TomlConfig.java
Remove TOML parser warning and loggerjava/src/org/openqa/selenium/grid/config/TomlConfig.java