JudahGabriel/ravendb — pull request #2 by kijanawoodard (2013-09-24 23:16:28+00:00)
Title: user info dumps json on screen

The "user info" is dumped onto the status view.

I didn't go much further in order to get some direction first.

- do you want to modify raven.js for each function like this or allow Fetch requests from other modules?

- should there be a consistent way to keep "active database" up to date? am looking at adding it to status routing, but not sure that is "great".

- earlier today, i went down the path of making each of one these status pages it's own route and doing a ko compose for the menu. it was ok, but the shell menu iterates all routes. i didn't want to mess with that off the bat. what do you think about having these each separate? it's a bit awkward thinking about what to do with these different unstructured views. i copied "documents" for app structure, but on that page, each collection is rendered with the same widget. i suppose the "view name" could determine a widget to render, etc.

- am i supposed to be checking in ,js and .js.map files or should those be excluded from git and created during build?