This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 24548 - When naming a class, check for obvious name errors
Summary: When naming a class, check for obvious name errors
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: archivesupport (show other bugs)
Version: 3.x
Hardware: Sun SunOS
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-07 20:22 UTC by Torbjorn Norbye
Modified: 2007-09-17 21:50 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Torbjorn Norbye 2002-06-07 20:22:37 UTC 
I created a SystemAction using the apisupport
template.
In the "Name" field, I entered "ExpandAction". I
didn't realize
the templates would add "Action" to whatever I
named - I
ended up with a class named "ExpandActionAction".
I couldn't
just rename this back to ExpandAction because this was
used in the code as well
(NbBundle.getMessage(ExpandActionAction.this
or something like that) and Rename didn't catch
that (we don't
have proper refactoring yet.)

Please enhance this such that if the name already
ends with
"Action", don't append "Action" to it.

I'm sure this generalizes to other cases as well,
perhaps
even outside the apisupport module, but I don't
have any
specific cases in mind.
Comment 1 Jiri Prox 2007-09-17 21:50:22 UTC 
Obsolete milestone, please reevaluate