LiftScreen field declaration API with type parameters
44 views
Skip to first unread message
Sergey Trofimov
Jun 13, 2011, 8:01:54 AM6/13/11
to lif...@googlegroups.com
Hello.
I see that some of field declaration methods have type parameters (like select[T](...), multiselect[T](...)) and others don′t (like radio(...)).
Is it intentional or it can be unified?
Also radio(...) is documented with “@param f a PairStringPromoter (a wrapper around a function) that converts T => display String” which is not used in the method declaration.
I see that some of field declaration methods have type parameters (like select[T](...), multiselect[T](...)) and others don′t (like radio(...)).
Is it intentional or it can be unified?
Also radio(...) is documented with “@param f a PairStringPromoter (a wrapper around a function) that converts T => display String” which is not used in the method declaration.
David Pollak
Jun 13, 2011, 2:08:47 PM6/13/11
to lif...@googlegroups.com
Feel free to open a ticket requesting this feature at http://ticket.liftweb.net (you must be a watcher of the LiftWeb space on Assembla to open tickets).
--
Lift, the simply functional web framework http://liftweb.net
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To view this discussion on the web visit https://groups.google.com/d/msg/liftweb/-/LXyysXTqPyYJ.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
--
Lift, the simply functional web framework http://liftweb.net
Sergey Trofimov
Jun 14, 2011, 2:40:12 AM6/14/11
to lif...@googlegroups.com
Ticket is opened https://www.assembla.com/spaces/liftweb/tickets/1042-unify-liftscreen-field-declaration-api-with-type-parameters
Reply all
Reply to author
Forward
0 new messages