[java] Point made as immutable

[mk868]

User description

Motivation and Context

Immutable objects help prevent unintended side effects - for example, using a mutable Point as a key in a HashMap<Point, Object> can lead to unexpected behavior if the point is modified after insertion.

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.

---

PR Type

Enhancement

---

Description

• Made the Point class immutable by declaring fields x and y as final.

• Updated the class-level Javadoc to better describe its purpose.

---

Changes walkthrough 📝

	Relevant files
Enhancement	Point.java Made `Point` class immutable and updated documentation      java/src/org/openqa/selenium/Point.java Changed x and y fields to final for immutability. Updated Javadoc to clarify the purpose of the Point class. +3/-3

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review API Compatibility Making fields final is a breaking change that could affect clients that directly modify x and y fields. Consider if this needs to be marked as a breaking change in the PR description. public final int x; public final int y;

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Encapsulate immutable fields Making fields final is good for immutability, but they should also be made private with getter methods to fully encapsulate the class and prevent direct access to the fields. java/src/org/openqa/selenium/Point.java [27-28] -public final int x; -public final int y; +private final int x; +private final int y; +public int getX() { + return x; +} + +public int getY() { + return y; +} + Apply this suggestion Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that while making fields final improves immutability, proper encapsulation requires private fields with getter methods. This follows object-oriented best practices and would prevent direct manipulation of the coordinates while still allowing read access.	Medium
More

[pujagani]

Thank you! @mk868