You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Daniel Keir Haywood (Jira)" <ji...@apache.org> on 2020/03/19 13:07:00 UTC

[jira] [Closed] (ISIS-156) [WON'T FIX] Renaming getName() and other methods in metamodel

     [ https://issues.apache.org/jira/browse/ISIS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Keir Haywood closed ISIS-156.
------------------------------------
    Resolution: Won't Fix

> [WON'T FIX] Renaming getName() and other methods in metamodel
> -------------------------------------------------------------
>
>                 Key: ISIS-156
>                 URL: https://issues.apache.org/jira/browse/ISIS-156
>             Project: Isis
>          Issue Type: Improvement
>          Components: Isis Core
>    Affects Versions: 0.1.2-incubating
>            Reporter: Daniel Keir Haywood
>            Assignee: Daniel Keir Haywood
>            Priority: Trivial
>
> from email exchange on mailing list:
> >
> > Just completing change for spec names.  To confirm that name == singular
> > name, what we have at the moment is:
> >
> >    getFullName - fully qualified class name
> >    getShortName - class name only
> >    getName - singular name with spacing
> >    getPluralName - the pluralised version with spacing
> >
> > It seems we have redundancy all along.
> >
> Yup, that's what we have.  Did mean to rename 'getName' to
> 'getSingularName', but I guess I forgot.  I'll go ahead and do that.
> > They are two types of name though which isn't obvious from the method
> > names. The first two are actually identifiers and won't change, whereas the
> > other two are dynamic and will change, especially on a localised client.
> > We might want to reflect this with getFullIdentifier and
> > getShortIdentifier.
> >;
> That's a good idea.  I'll make that change too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)