Types on documents

[stuartpb]

Since we're about to start mixing in users and (potentially) channels documents, we should start putting a type on each document, so as to make excluding documents from views easier.

[stuartpb]

Also probably going to get stored as a document in the database: the migration plan. Having it be localStorage is... weird.

[stuartpb]

So, the types will be:

• users
• channels
• plan
• messages

Where the first 3 go on the documents of the same name, and messages goes on everything else.

[stuartpb]

Looks like the way I went was to make a document called "metadata" that has both "channels" and "users" objects... yeah, now that I think about it, I'm going to split those into two docs, because I'm going to need channels a lot more than I'm going to need users.

[stuartpb]

Though, ugh, that means having a weird Pouch-wrapping-object around both of 'em, each basically only having one property...

Nope, still doing it. I don't want a perf hit from having to deal with Slack groups of several-thousand-users but only a few channels, or vice versa, when I need to do operations that wouldn't otherwise take a hit.

[stuartpb]

But they really only get dealt with simultaneously...

Ugh, fine, I'll make it one object.

[stuartpb]

So anyway, I'm thinking about changing the slack metadata from "metadata" to "slack-metadata", and making it so that doc and plan both have a type of metadata.