Summary: | [organize imports] should allow to filter forbidden and discouraged types | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> | ||||
Component: | UI | Assignee: | Markus Keller <markus.kell.r> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P3 | CC: | akiezun, juergen, markus.kell.r, martinae | ||||
Version: | 3.4 | ||||||
Target Milestone: | 3.7 M5 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Bug Depends on: | 296277 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Dani Megert
2008-02-11 06:57:20 EST
At least, the dialog should show good types before discouraged and forbidden types. There's no API to compute access rules on TypeNameMatch cheaply, see bug 264695. The other bug is actually another problem. Field bug 296277 for new JDT/Core API. I think we should generalize the settings for access restrictions from the 'Java > Editor > Content Assist' page. E.g. move the 'Hide forbidden/discouraged references' checkboxes to the Type Filters page. >I think we should generalize the settings for access restrictions from the
>'Java > Editor > Content Assist' page. E.g. move the 'Hide
>forbidden/discouraged references' checkboxes to the Type Filters page.
Sounds reasonable to me.
Should look at this together with the bugs concerning type filters and relevance. *** Bug 91683 has been marked as a duplicate of this bug. *** Created attachment 184851 [details]
Fix
Fixed in HEAD (and fixed a conflicting mnemonic). Fixed failing test in OptionsConfigurationBlockTest. ... and updated Type Filters preference page description in PreferencesMessages.properties (In reply to comment #8) > Created attachment 184851 [details] [diff] > Fix This is only the preference file and not the full fix. Marking as obsolete. Verified in I20110124-1800. |