Skip to content

Javadoc for NavigableExpression and Path - #1541

Open
njr-11 wants to merge 2 commits into
jakartaee:mainfrom
njr-11:javadoc-for-navigable-expression-and-path
Open

Javadoc for NavigableExpression and Path#1541
njr-11 wants to merge 2 commits into
jakartaee:mainfrom
njr-11:javadoc-for-navigable-expression-and-path

Conversation

@njr-11

@njr-11 njr-11 commented Aug 21, 2026

Copy link
Copy Markdown
Member

Add Javadoc for NavigableExpression, Path, and one of the Path subclasses. After getting that correct, the same can be applied to the other Path subclasses

njr-11 added 2 commits August 21, 2026 13:27
Co-authored-by-AI: IBM Bob 2.0.2
Co-authored-by-AI: IBM Bob 2.0.2
@njr-11 njr-11 added the documentation Improvements or additions to documentation label Aug 21, 2026
Comment on lines +37 to +38
* An {@linkplain Expression expression} that navigates to an attribute of an
* embeddable or association.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure this is the right way to say it.

  • I don't think we define the term "embeddable" anywhere in Jakarta Data
  • it's not the expression itself that navigates an attribute or association; the expression represents a type which allows such navigation

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not the expression itself that navigates an attribute or association; the expression represents a type which allows such navigation

well, actually scratch what I said ... I suppose this is actually correct but somehow I still find it confusing....

*
* <p>
* The {@code navigate} methods accept a metamodel attribute of an intermediate
* type {@code U} and return a new expression of a more specific subtype,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think "more specific subtype" is quite correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants