-
Notifications
You must be signed in to change notification settings - Fork 76
Correctly handle Javadoc method link #160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
richardimaoka
wants to merge
2
commits into
lightbend:master
from
richardimaoka:javadoc-directive-for-method-richard
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(current) https://docs.oracle.com/javase/8/docs/api/?java/io/File.html#pathSeparator
jumps to the class page,
(expected) https://docs.oracle.com/javase/8/docs/api/java/io/File.html#pathSeparator
correctly jumps to the method section of the page
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original behaviour of linking to the javadoc with frames comes from this suggestion by @jroper : #52 (comment)
I am not sure if there even exists a way to link to methods when opening with frames.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As @jonas points out, this change results in a terrible user experience. Out of the box there doesn't exist a way to link to methods when opening with frames, but we have this Javascript code that gets added to every page in the Lagom Javadocs:
https://github.com/lagom/lagom/blob/fde496bc089157e40a3a132a3ae1cf0d5f1111d4/project/Doc.scala#L63-L79
This then gets configured here:
https://github.com/lagom/lagom/blob/fde496bc089157e40a3a132a3ae1cf0d5f1111d4/project/Doc.scala#L134
That way, you can link to methods in the docs, and still have it open with frames.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, let me look at how lagom works for this.