data store - Githubissues

cch5ng / fe_interview

[wip] revamp of front end interview app

https://fe-interview.herokuapp.com

2 stars 0 forks source link

data store #2

Open cch5ng opened 5 years ago

cch5ng commented 5 years ago

[x] script to populate question table with json data
- probably would be more efficient to revise the data parsing script to generate one single list of questions (one file, not multiple files per category)
[ ] doc dependency on secrets file (provide a template for it)
[x] fix db owner (#10)
- affects secret (config) and also db setup script
[x] script to drop/create db
[x] scripts to create tables
[x] update the package.json scripts to run a configure_db.js script

starting out with 4 tables;

pretty basic but need to extend it a little for the feature of tracking test results (like I think it is most useful for the job applicant to be able to track over practice sessions which topics they are not doing very well in)

cch5ng commented 5 years ago

misc thoughts

something like react/mobx (state tree) node (or graphql) /postgresql ... might want to use json server initially? then refactor to rest api/graphql?

lib: auth0

messy point: is when the source control gets out of sync with user's saved questions; how to handle this? ability to save archived/obsolete questions and tracking which questions were deprecated at source

cch5ng commented 5 years ago

notes:

keywords user and order should not be used as custom tables or columns

cch5ng commented 5 years ago

missing app/index.js (and object related files)

missing bin/server.js

missing secrets file

cch5ng commented 5 years ago

in terms of seeding data, not sure what is way to proceed

just write a node script (use pg to interact with postgress)
- run the node script manually at start of setup
OR write another bash script that triggers a node script (need some js interpretation b/c data is js/json) ... maybe this is too many unnec steps

cch5ng commented 5 years ago

thought 012119 > 12p ish

reuse the pattern of /app/dragon/table.js file ... initially called by seed script (need to import the output js/json files from the init parsing script results)

debug 2 issues

specified ID in db as SERIAL (implies number) but I was seeding with str id's; not sure if I need to track my string id as well as the database id...
also sql syntax was wrong (passing into the pg query function); was missing the col names in init sql

cch5ng commented 5 years ago

issues:

[x] something is wrong with the coding questions (think the mapping is off or something)
[x] category is not getting populated