Just that it was a bad convention in the first place, and it's time we
stopped adding to the problem.  The fact our entities are stored in
Hibernate is just an implementation detail.


On 2013-08-01 14:07, David Mason wrote:
> In zanata-model/src/main/java/org/zanata/model/tm/TransMemory.java:
> 
>> +import lombok.Data;
>> +import lombok.EqualsAndHashCode;
>> +import lombok.Setter;
>> +import lombok.ToString;
>> +
>> +/**
>> + * A translation Memory representation.
>> + *
>> + * @author Carlos Munoz <a href="mailto:camunoz@redhat.com">camunoz@redhat.com</a>
>> + */
>> +@Entity
>> +@EqualsAndHashCode(callSuper = true, of = {"description"})
>> +@ToString(exclude = "translationUnits")
>> +@Data
>> +@Access(AccessType.FIELD)
>> +public class TransMemory extends SlugEntityBase implements HasTMMetadata
> 
> What is the reason for breaking from the HFoo naming convention for
> entities here? It's confusing to have this one thing different from all
> the other entities.
> 
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/zanata/zanata-server/pull/78/files#r5522052>.
> 


-- 
Sean Flanigan

Senior Software Engineer
Engineering - Internationalisation
Red Hat