20 Jan
2014
20 Jan
'14
4:17 a.m.
Yes please.
I don't think a "warning" is best, but more like an informative helpful
message, something along the lines of: this class doesn't have any
properties yet, you can add some below, property names should follow the
following rules, you can set a user friendly name afterwards, and until
you add some properties, this isn't really a class which you can use.
This acts both as a warning and short inline documentation.
On 01/19/2014 06:17 PM, Paul Libbrecht wrote:
that means that the class editor should really show a
warning about the class not existing yet when I have used
/xwiki/bin/edit/XWiki/ClassSheetBinding?editor=class
shall I open an issue?
paul
Le 20 janv. 2014 à 00:01, Marius Dumitru Florea <mariusdumitru.florea(a)xwiki.com> a
écrit :
>> Rationale:
>
>> - don't trust marker classes (maybe they don't exist?).
>
> They don't exist. You cannot create an XClass with no properties.
>
>> - wish that the object editor indicates it, when an object is presented
> whose class is missing
>
> I agree. The object editor just shows them as deprecated I think, because
> it doesn't find them in the class as the class is an empty document as
> return by $xwiki.getDocument() when a document doesn't exist.
>
>> , maybe also when the class-editor is used for the first time on a given
> page.
--
Sergiu Dumitriu
http://purl.org/net/sergiu