• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Opinion on ERXKey type parameterization
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Opinion on ERXKey type parameterization


  • Subject: Opinion on ERXKey type parameterization
  • From: Paul Hoadley <email@hidden>
  • Date: Mon, 27 Mar 2017 14:40:33 +1030

Hello,

Say I have a ‘Foo' entity, with a to-many relationship ‘bars’ to a ‘Bar’ entity. Every Velocity generation template I’ve ever seen will output something like:

  public static final ERXKey<Bar> BARS = new ERXKey<Bar>(“bars”);

or, even better:

  public static final ERXKey<Bar> BARS = new ERXKey<Bar>(“bars”, ERXKey.Type.ToManyRelationship);

But shouldn’t ERXKey there be parameterized as ERXKey<NSArray<Bar>>? Admittedly, I’m struggling to see where it would make a huge difference—but just for completeness?


--
Paul Hoadley
http://logicsquad.net/



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


  • Follow-Ups:
    • Re: Opinion on ERXKey type parameterization
      • From: Samuel Pelletier <email@hidden>
    • Re: Opinion on ERXKey type parameterization
      • From: Matthew Ness <email@hidden>
  • Prev by Date: Re: Set case insensitive unique index with ERXMigrations
  • Next by Date: Re: Set case insensitive unique index with ERXMigrations
  • Previous by thread: Off Topic
  • Next by thread: Re: Opinion on ERXKey type parameterization
  • Index(es):
    • Date
    • Thread