Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346238 - [Xtend] Avoid cutting the "is" prefix in case of extensions
Summary: [Xtend] Avoid cutting the "is" prefix in case of extensions
Status: VERIFIED FIXED
Alias: None
Product: Xtend
Classification: Tools
Component: Core (show other bugs)
Version: 2.2.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: v2.7
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-18 09:27 EDT by Markus Voelter CLA
Modified: 2014-08-22 06:06 EDT (History)
3 users (show)

See Also:

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 Markus Voelter CLA 2011-05-18 09:27:15 EDT 
I create an Xtend 2 method isXXXX(Metaclass) in an Xtend class and inject this this class as an extension into another one. The isXXX method is now available as XXXX on the Metaclass instances However, I suggest the "is" should not be removed, because that removes the "hint" that XXXX is a predicate. Removing a "get" makes sense, but removing the "is" doesn't.
Comment 1 Sebastian Zarnekow CLA 2011-07-29 18:10:49 EDT 
ContentAssist should prefer the #isSomething version over #something or #isSomething(). However, the *SugarDescriptionProvider should still be conformant to the JavaBeans conventions.
Comment 2 Sven Efftinge CLA 2011-10-25 02:50:39 EDT 
no more features in 2.1
Comment 3 Stefan Oehme CLA 2014-08-21 14:45:34 EDT 
CA now keeps isXXX if you typed the is prefix.