-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Types on documents #12
Comments
Also probably going to get stored as a document in the database: the migration plan. Having it be localStorage is... weird. |
So, the types will be:
Where the first 3 go on the documents of the same name, and |
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 |
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. |
But they really only get dealt with simultaneously... Ugh, fine, I'll make it one object. |
So anyway, I'm thinking about changing the slack metadata from "metadata" to "slack-metadata", and making it so that doc and |
Since we're about to start mixing in
users
and (potentially)channels
documents, we should start putting atype
on each document, so as to make excluding documents from views easier.The text was updated successfully, but these errors were encountered: