Help test release candidates for Meteor 1.0.4!

[glasser]

@moretti Is this a regression in the 1.0.4 RC series? ie, does it work in 1.0.3.2 but not in one of the 1.0.4 RCs? If so, please report it on the tracking issue on GitHub at https://github.com/meteor/meteor/issues/3814

(Ideally with a reproduction following the guidelines at https://github.com/meteor/meteor/wiki/Contributing-to-Meteor#reporting-a-bug-in-meteor but starting with just a note that there’s a regression is fine.)

[sashko]

This is the intended usage, since the rendered callback is expected to run only once and not rerun. By the way it would be better to use this.autorun here instead of tracker.autorun - I’ll add an example to the docs.

[moretti]

@glasser, I’ve had just created the reproduction when @sashko the expected behavior.

@sashko, thanks! So, can I keep it this way (with this.autorun) or it will be a better way to subsbcribe inside a template?

[glasser]

@sashko Is this an intended change in 1.0.4, then? Do we need to make sure it’s in History.md?

[sashko]

I’m not sure exactly what we are talking about - the rendered callback was never reactive. Only helpers are.

I don’t think there are any changes in this area. @moretti yes I think you have the intended usage.

[Maaz]

I thought the blaze changes with the additional subscribe method on the template was suppose to replace what you’re trying to do.

Template instances now have a subscribe method that functions exactly like Meteor.subscribe, but stops the subscription when the template is destroyed. There is a new method on Template instances called subscriptionsReady() which is a reactive function that returns true when all of the subscriptions made with TemplateInstance#subscribe are ready. There is also a built-in helper that returns the same thing and can be accessed with Template.subscriptionsReady inside any template.

I assume this would be the best practice for template level subscriptions going forward.

[moretti]

@Maaz, could you give me an example of how you would do this subs?

Tks

[Maaz]

I haven’t tried it myself yet but it’s intended to work exactly like Meteor.subscribe so take a look at the documentation for that: http://docs.meteor.com/#/full/meteor_subscribe

You can use the following methods to figure out if your subscriptions are ready:

There is a new method on Template instances called subscriptionsReady() which is a reactive function that returns true when all of the subscriptions made with TemplateInstance#subscribe are ready

I can’t provide a concrete example because I haven’t tested it for myself yet.

[sashko]

There will be new documentation when https://docs.meteor.com is updated for the new release!

[dcsan]

is there a prerelease of the docs anywhere? I recall there were a bunch of interesting new API changes around data and template >
https://github.com/meteor/meteor/blob/release-1.0.4/History.md#blaze
but not sure if they’re part of this release. I didn’t see it in the release notes.

specifically around cleanup of the api around template.instance() vs. .data()
or maybe I’m getting blurred between a discussion and what’s actually here.

[glasser]

Good call, I’ve deployed the current docs to https://docs-104rc.meteor.com/

Which changes are you referring to? We had a change to how currentData/parentData worked in event handlers that’s not backwards-compatible that we reverted. But we did fix a related bug, as described in the release notes.

[bobmonsour]

I’m thrilled to see Accounts.onLogin(func) now available on the client. Many thanks MDG!

[Ben]

It’s totally possible that it was always there and I’ve just completely missed it before, but I suddenly see a new (empty) mongo collection in Mongo called “meteor_accounts_loginServiceConfiguration”? Is that one needed?

[glasser]

It’s where the configuration for oauth login methods like Facebook are stored. It’s been around for forever, but the change in this release is that we ensure it has an important index, which means it gets created earlier.

It should only exist for apps using accounts. If your app doesn’t use accounts, that’s a bug.

Technically we could try to avoid creating it if you’re only using password login but that would make the dependencies more complicated and I don’t think having an empty collection is a big deal.

[stachrom]

How do i run 1.0.4-rcx with xmlbuilder? (–> https://github.com/oozcitak/xmlbuilder-js)

There was no problem with meteor 1.0.3.2 and xmlbuilder version 2.4.5

xmlbuilder version 2.4.5 does not work with meteor 1.0.4
xmlbuilder version 2.6.2 (latest) does not work with meteor 1.0.3.x or meteor 1.0.4

error: conflict: constraints on xmlbuilder cannot be satisfied.
Constraints come from:

Regards roman

[glasser]

@stachrom Can you show a full reproduction as explained in https://github.com/meteor/meteor/wiki/Contributing-to-Meteor#reporting-a-bug-in-meteor ? I’m having trouble understanding exactly what you’re trying to do. And if this is a regression in 1.0.4, please report it on the GitHub issue, not here.

[glasser]

1.0.4 is released! Thanks for all your help.

Known slight issue: if you’re going to http://docs.meteor.com (not https) it may not update you from 1.0.3.2 to 1.0.4 docs (issue with appcache vs force-ssl).

[jaaprutten]

Any idea when Crosswalk is officially supported by Meteor? We can’t wait to use if for our mobile app made with Meteor