Hi guys,
maybe I'm not getting something crucial but as far as I can see, the Heist APIs changed a lot from 0.8 to 0.10. The most relevant example is that:
Does not exists anymore. So far so good, being 0.8 the last stable release, but with the 0.10 release a lot of website documentation will become stale.
Take a look here:
http://snapframework.com/docs/tutorials/heist
At the bottom of the site you'll see the old API gets called.
I suggest we create another branch for this temporary transition, so we can update all the due documentation, preserving the stable one until 0.10 is released. Once 0.10 is out, simply merging from 0.10 to master will update the site with the correct APIs and infos. This applies also for snap,
because now wrapHandlers is gone. When snap 0.10 will be out, we need also to change every occurrence of wrapHandlers to wrapSite.
Obviously I can create this branch locally and then pull req everything when the time will come.
What do you reckon?
Hi guys,
maybe I'm not getting something crucial but as far as I can see, the Heist APIs changed a lot from 0.8 to 0.10. The most relevant example is that:
Text.Templating.HeistDoes not exists anymore. So far so good, being 0.8 the last stable release, but with the 0.10 release a lot of website documentation will become stale.
Take a look here:
http://snapframework.com/docs/tutorials/heist
At the bottom of the site you'll see the old API gets called.
I suggest we create another branch for this temporary transition, so we can update all the due documentation, preserving the stable one until 0.10 is released. Once 0.10 is out, simply merging from 0.10 to master will update the site with the correct APIs and infos. This applies also for snap,
because now wrapHandlers is gone. When snap 0.10 will be out, we need also to change every occurrence of wrapHandlers to wrapSite.
Obviously I can create this branch locally and then pull req everything when the time will come.
What do you reckon?