eclipse-jdt / eclipse-jdt/eclipse.jdt.core

Feature: Add linebreaks to error message

Open
#1,422 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
237
Forks
195
Avg merge
1d 10h
Merged PRs (30d)
49

Description

See screenshot:
![grafik](https://github.com/eclipse-jdt/eclipse.jdt.ui/assets/990869/062684fc-e7b0-4550-8944-0f2d5a34725d)

It's extremely hard to find out, which NonNull is causing the error/warning. Could you please add a line break right before inserting the type definition, so they both begin on a new line like this:
```
Null type safety (type annotations): The expression of type
'@NonNull Comparator>>' needs unchecked conversion to conform to
'@NonNull Comparator>>'
```
As a bonus feel free to add any whitespace alignment, highlighting or other comparison helper ...

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named in the issue. Start by locating the diagnostic text for the null type safety message in the Java compiler sources and its existing tests; done means the type definition begins on a new line and the diagnostic tests pass with the updated wording.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
compilers
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.