Idea: could the XML bind code be turned into a module or standalone library of some kind?
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
We can just move the APIs someplace else in Lift other than Helpers... it's not taking up that much space.
But having a silent breaking change (Wizard and Screen stuff just not working anymore) is really suboptimal.
At the very least, we should have something during the boot phase that looks for common Wizard default templates and throws an exception if they are using the old XML bind tags. Finding out from a production user that stuff simply doesn't work after the security-related upgrade on a Lift 3.0 codebase is wicked, wicked lame.
--
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.
Antonio
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
Antonio
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
Antonio
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+unsubscribe@googlegroups.com.
--
Antonio
Antonio
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
--
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
On Sunday, April 26, 2015 at 2:50:33 AM UTC-4, David Pollak wrote:We can just move the APIs someplace else in Lift other than Helpers... it's not taking up that much space.Absolutely down to move this to a module (whether external or still managed in Lift's core build pipelinedoesn't really matter to me), but having two completely different approaches for template management inthe core framework is more confusing than useful, IMO. Obviously we want to make sure everything that'sthere still works—and migration away from them is a big part of why we made a stable M0/M1 release thatpreceded those changes. More on the interaction of that with the security patches below.But having a silent breaking change (Wizard and Screen stuff just not working anymore) is really suboptimal.I think it's just wizard that suffers from this. We communicated that LiftScreen switched to CSS selectors,and I believe this is a compilation-breaking change for people who were using LiftScreen internally. I did not,however, realize that wizard was built in such a way that it relied on BindHelpers without failingloudly in client code when BindHelpers was removed. Looks like this was a bit thing we missed when wemade the CSS LiftScreen the main implementation, and even though a lot of those changes were open onGithub for a while and existed on the snapshot before going into a milestone build, I suspect no one whouses wizard was on snapshot to find the breakage.At the very least, we should have something during the boot phase that looks for common Wizard default templates and throws an exception if they are using the old XML bind tags. Finding out from a production user that stuff simply doesn't work after the security-related upgrade on a Lift 3.0 codebase is wicked, wicked lame.That's fair, and I suppose it's the big hunking drawback for how long our Lift 3 release cycle has gone—production apps on a really old build of a next major version that's only halfway through removing thethings that are deprecated in the previous major version.
I wouldn't be at all opposed to making an M1-1 build that included our XML patches over the M1 build.Being on the hook for security patches to M1 until we've got all the proper migration pieces in place forthe Lift 3 final release seems pretty reasonable.Thanks,Antonio
--