Don't expose collections directly

[stubailo]

Collections - don't expose the collection directly, have an API for talking to it in case you need to change the schema or guarantees later

[stubailo]

@tmeasday do you think this is a good idea? This is in the "building a package" outline.

[tmeasday]

I'm not quite sure what this means in practice. You mean that we wouldn't have a exported symbol called Todos? How would you do queries?

[stubailo]

Well the idea is, you would have methods on Todos like: Todos.getInList(listId) instead of Todos.find({ listId: listId })

This way you could switch to another DB more easily? Not sure how realistic it is.

[tmeasday]

My sense is it's too much of a departure from how people typically do things at this point in time.

[stubailo]

OK sounds good. It's just something we ran into twice:

1. When converting Todos to use SQL
2. When we wanted to change how Accounts worked internally, it was tough that we exposed Meteor.users as an API

[tmeasday]

I think it makes a heap of sense for point 2., but gets to the larger discussion of saying users shouldn't use the users collection...

[stubailo]

Yeah but the point still stands that it's too different from what people do now.

[tmeasday]

Yep, put it on the ideas list for guide v2 :)