On Tue, Nov 17, 2009 at 10:06 PM, Joni Freeman <[email protected]>wrote:
> On 18 marras, 01:10, David Pollak <[email protected]> > wrote: > > I'd like to see the JSON stuff moved from Option to Box, but that's > Joni's > > call. > > Hi, > > I do not agree. We have quite a lot of lift-json users who do not yet > use other parts of Lift, and Box is not a familiar construct outside > of Lift. I really like to keep it that way. But could lift REST APIs > wrap the lib to provide more Liftesque API? > It's more of a return-type issue. The reason I created Box in the first place is that Option doesn't give you the ability to capture reasons for None (yeah, there's Either... although there wasn't when I introduced Box [Can at the time], but you can't use Either in a for comprehension). In reviewing the JSON code, there's actually nothing that I'd change in the APIs. I would support Box everywhere there's support for Option (serializing/deserializing and implicit helpers). > > Cheers Joni > > -- > > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=. > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=.
