Open Rebolon opened 10 years ago
Although we're aware of the issues, we're focusing on 0.4.x. We would merge a PR that updates 0.3.7 to work with Blaze, but it's not a priority. 0.4.x is about 90% stable at the moment, by which I mean it is stable and the API is unlikely to change much more, but it lacks some key tests and we still plan a couple small rewrites of pieces of the internals. I would personally not use it for production data quite yet because a few of the properties stored in mongo will likely change names soon.
ok, hope there will be a quick tuto on how to migrate from 0.3 to 0.4 If i have time, i may do a PR. Thanks
Benjamin RICHARD about.me/benjamin.richard/
2014-04-16 17:10 GMT+02:00 Eric Dobbertin notifications@github.com:
Although we're aware of the issues, we're focusing on 0.4.x. We would merge a PR that updates 0.3.7 to work with Blaze, but it's not a priority. 0.4.x is about 90% stable at the moment, by which I mean it is stable and the API is unlikely to change much more, but it lacks some key tests and we still plan a couple small rewrites of pieces of the internals. I would personally not use it for production data quite yet because a few of the properties stored in mongo will likely change names soon.
— Reply to this email directly or view it on GitHubhttps://github.com/CollectionFS/Meteor-CollectionFS/issues/284#issuecomment-40610537 .
I've done almost all corrections for Blaze compat. i've started from tag v0.3.7 but on which branch can i do a Pull request ?
https://github.com/Rebolon/Meteor-CollectionFS/tree/feature/BlazeUpdateOldAPI
master
is still 0.3.7
I've migrate my app to meteor 0.8, unfortunately, CollectionFS 0.3.7 is not compatible with that version of meteor. The problem comes from collectionFS_templates.html file where it uses {{{attributes}}} inside an HTML node whereas it's now forbidden by Blaze.
Is the CollectionFS v0.4.x stable enough to think to an update of the app or should correct the collectionFS v0.3.x for Blaze ?