Closed psawaya closed 10 years ago
This looks fantastic. I've only glanced at the code, and it looks good except one question: I haven't seen such a services.json file made available in a URL (maybe because I don't do much web programming). Is there a reason to do it this way? Instead of, say, in the dashboard() function grabbing the info from a database and creating a JSON object and passing that to the template? My intuition is to lock down the number of visible URLs -- especially ones with raw data -- but I suppose it doesn't matter much.
I'm going to leave this issue open for my purposes but you can consider the requirement satisfied.
Yes, I think you'll eventually want to create services.json from the database. It will make the page will load faster (and eliminate one externally visible URL) if you generate the services object in a script tag instead of a JSON file, so that may be a good idea. Additionally, you might want to look at something like underscore for templating.
name of data source
icon associated with data source
type of data source (of three types: oauth, scraping, manual upload) that render appropriate modal interfaces