Antonio Salazar Cardozo
Antonio Salazar Cardozo
@fmpwizard It looks like you'd originally been meaning to look at this. Do you think you'll have time? If not that's fine, I'll try and make some time at some...
I'll try and eyeball this guy soon.
It conceptually bugs me that we're using a two-form solution, and it's a usability issue for the default state to be enter not submitting, even in some browsers… Let's keep...
The biggest question here is the syntax to be used. You can use `"selector " #> `, for example, to surround the children of the selected element with a `div`...
Notably, Lift 3 supports a `template` parameter that can be passed to the `lazy` snippet. It doesn't support customization of the timeout, though. We'd need to support that directly in...
The basic question here is what we do when we have a `JValue` bundled with a `JsCmd` in the return value of `liftSession.runParams`. This seems like it's mostly a concern...
Can't you now hook into `onBeginServicing` and `onEndServicing` to basically do exactly this? I guess these two miss the actual sending of the response…
Some deeper investigation revealed that paranamer or reflection (not sure which yet) is reporting that the `Long` parametrized type is instead a `java.lang.Object`: `scala.collection.immutable.List`.
Handy workaround! Did you happen to look into fixing it at the `lift-json` level at the time or not?
Ironically I just realized 1768 was linked to this bug, but 1768 not only doesn't fix this bug, it actually pulls the issue further up the chain by making it...