Community
Participate
Working Groups
From Bug 414237 Using the JDT editor on a class with non-null annotations, F3 on a declaration with external annotations should open a 'read-only' editor/viewer somewhat like the class file viewer. This editor/viewer should render the external non-null annotations in traditional @NonNull form. This editor/viewer should be titled to clarify that the editor/viewer is for a class X viewed from the annotation path of bundle Y. It would be nice if the editor/viewer used a distinctive case/font/color for the contributions of the external annotations. Perhaps everything other than the external annotations is partially greyed out. It would be nice if the editor/viewer permits the external annotations to be edited. It would be nice if the editor/viewer provides navigation to related editors/viewers for the same class viewed from other annotation paths. It would be nice if the hovertext for an external @NonNull identified the annotation path entry that contributed it.
(In reply to Ed Willink from comment #0) > From Bug 414237 Correction: from Bug 466299#c22
Wouldn't implicit annotations (inherited, from @NonNullByDefault, or from external annotations) make a wonderful use case for code mining?
FYI. I never use @NonNullByDefault since I cannot tolerate the risks that will occur in the perhaps 1% of legacy usage where @Nullable is appropriate. Equally I find secret declarations inherently dangerous/confusing. (Until the platform and EMF are @NonNull'd, all my code has to be legacy compatible.) I see a number of 'source synthesis' bugs whereby my explicit @NonNull gets doubled up. Waiting for more important bugs to fix up first.
