This project was generated with Angular CLI version 7.3.0.
to do: keep list of active users by tying user to websocket also tie user to spotify acct to get profile link + pic might need to use server side tokens instead of client side auth is long rebuild time new? check build before heroku setup
board:
fix bug when drag path includes top left tile
move board calc to server :()
To get https:// and spotify login working locally, add the localhost.crt file as a trusted certificate
Run ng serve --proxy-config proxy.conf.json --ssl --ssl-key ./localhost.key --ssl-cert ./localhost.crt
for a dev server.
Navigate to https://localhost:4200/.
The app will automatically reload if you change any of the source files.
Run server with zero in /zero_server.
Install zero on command line separately with npm install -g zero
Server should be running at http://localhost:3000.
run other server with node chat.js in /ws_server
Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.
Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via Protractor.
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.
GET /users/all returns [{username: string, userId: number, spotifyProfile: ??}]
GET /users/online returns [{username: string, userId: number}]
GET /user/:userId returns User
GET /user/ returns new User
POST /user/ accepts User} returns User
GET /user/:userId/state returns ??
POST /user/:userId/state ?? ??
--
GET /chatHistory returns [{message: string, username: string, timestamp: string}]
--
GET /song/current returns {track: Track, offset_ms: number, startTime: string}
GET /song/pending returns [{track: Track, chosenBy:[{username: string, userId: number}], score: number]
POST /song/add {track: Track, user: {username: string, userId: number}} returns [{track: Track, chosenBy:[{username: string, userId: number}], score: number]
POST /song/choose {track: Track, user: {username: string, userId: number}} returns [{track: Track, chosenBy:[{username: string, userId: number}], score: number]
POST /song/vote/ {track: Track, user: {username: string, userId: number}, vote: number} returns [{track: Track, chosenBy:[{username: string, userId: number}], score: number]
Server: {type: 'chatMessage', payload: {message: string, username: string, timestamp: string}} responds with same message
Client: {type: 'chatMessage'} adds to message queue
spotify state can stay on client, should cache locally user state can stay on client, but no server persistent state means server should trust client or client should try relog on load
changing object specs is causing problems iron out what info is needed for each operation: