No error when a field-access element shares the same name as a parameter

[xterao]

Address an issue in DAO method argument usage validation where a method parameter was not error-highlighted if a field-access element invoked a property with the same name.

Update the logic that retrieves preceding elements under inspection to use the PsiTreeUtil API.

[Copilot]

Pull Request Overview

Addresses an issue where DAO method parameters weren’t flagged if accessed via a field on an object; updates the logic to use IntelliJ’s PsiTreeUtil.prevLeaf API when checking preceding SQL elements.

• Replace prevSibling and extension prevLeaf() calls with PsiTreeUtil.prevLeaf(...) in visitor, directive handler, and pattern util
• Update a test case to validate that a field-accessed property (employee.employeeName) is correctly treated as unused when the standalone parameter is provided

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
src/test/.../DaoMethodVariableInspectionTestDao.java	Updated SQL annotation and parameters in test to cover field access
src/main/kotlin/.../DaoMethodVariableSqlVisitor.kt	Swapped element.prevSibling for PsiTreeUtil.prevLeaf(element)
src/main/kotlin/.../common/sql/directive/DirectiveHandler.kt	Replaced extension prevLeaf() with PsiTreeUtil.prevLeaf(it)
src/main/kotlin/.../common/psi/PsiPatternUtil.kt	Changed prevLeaf() calls to PsiTreeUtil.prevLeaf(element)

Comments suppressed due to low confidence (1)

src/main/kotlin/org/domaframework/doma/intellij/inspection/dao/visitor/DaoMethodVariableSqlVisitor.kt:46

• [nitpick] Add a unit test covering cases where there is whitespace or comments between a field-access dot and the identifier to verify that the new prevLeaf logic still correctly recognizes the dot separator.

PsiTreeUtil.prevLeaf(element)?.elementType != SqlTypes.DOT