when will the main branch have the auth branch merged in?

37 views
Skip to first unread message

Joe

unread,
Sep 30, 2012, 8:41:53 AM9/30/12
to meteo...@googlegroups.com
any timeline? Thanks.

Zhang Hong

unread,
Sep 30, 2012, 8:46:07 AM9/30/12
to meteo...@googlegroups.com
add a wishlist + 1 too

在 2012年9月30日星期日UTC+8下午8时41分53秒,Joe写道:
any timeline? Thanks.

Nick Martin

unread,
Sep 30, 2012, 8:51:21 PM9/30/12
to meteo...@googlegroups.com
Hey all,

I can't give an exact timeline (software estimation is hard!), but I think we're closing in on merging auth to mainline meteor. There are a few more breaking API changes coming real soon now:

- Move everything from Meteor.accounts to Accounts, to be more parallel with things like Email, Session, etc. Hopefully this should be a simple search and replace for people.

- Change allow() API to allow() and deny(). The new API should be clearer and more expressive.[1]

After getting the API finalized, we have a few other tasks, for example, we still need to write documentation.

With all that said, I do feel we're getting very close. It won't be this week, but it is coming soon!


Hope that helps.
-- Nick


[1]: Hopefully implmenting this this week.
Old API:
- all allows return true, request is allowed
- request is denied.

New API adds 'deny', which takes the arguments as allow. The rules:
- any deny returns true, request is denied
- any allow returns true, request is allowed
- request is denied

This should be more straightforward to use. Every time you call deny you deny more things. Every time you call allow, you allow more things.


any timeline? Thanks.

--
You received this message because you are subscribed to the Google Groups "meteor-core" group.
To view this discussion on the web visit https://groups.google.com/d/msg/meteor-core/-/3uwmYvQVN3QJ.

To post to this group, send email to meteo...@googlegroups.com.
To unsubscribe from this group, send email to meteor-core...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/meteor-core?hl=en.

Reply all
Reply to author
Forward
0 new messages