-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8301813: Bad caret position in error message #12421
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
8301813: Bad caret position in error message #12421
Conversation
👋 Welcome back jjg! A progress list of the required criteria for merging this PR into |
@jonathan-gibbons The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
@jonathan-gibbons This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 23 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit d53ade1.
Your commit was automatically rebased without conflicts. |
@jonathan-gibbons Pushed as commit d53ade1. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review a trivial update to
DocCommentParser
and corresponding updates to tests, to fix the caret position in the two forms of the "no tag name found" error message.The fix is simply to use the overload of
erroneous
that allows the preferred caret position to be specified. This overload was not available at the time the affected lines were originally written.The "natural" place to test this is in the
doctree
tests (that is,TagTest.java
) but that test is not set up for easy monitoring of the end-user visible caret, so a new doclet test is created for that. (TestNoTagName.java
).BadPackageCommentTest.java is also affected. It is updated in a manner similar to that in a parallel PR for handling at-escapes. However, the changed caret position will eventually probably cause a minor change conflict that will need to be resolved.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12421/head:pull/12421
$ git checkout pull/12421
Update a local copy of the PR:
$ git checkout pull/12421
$ git pull https://git.openjdk.org/jdk pull/12421/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12421
View PR using the GUI difftool:
$ git pr show -t 12421
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12421.diff