Skip to content

Instantly share code, notes, and snippets.

View nwgambee's full-sized avatar

Noah Gambee nwgambee

View GitHub Profile

Dev.to Group Project - Week 3 Reflection

Daniel Frampton, Tristan Holtz, and Noah Gambee

Liked

- What did the team like about the last week?

  • We were happy with our communication and our flexibility in working between the FE and BE to accomodate each other's technincal needs
  • We stayed on top of switching between driver/navigator and divide/conquer
  • Worked on creating smaller PR's to keep issues easy to track and stay on top of what everyone is working on
  • Acccomplished what we set out to do (MVP) and managed time well
@nwgambee
nwgambee / svelte_router_setup.md
Last active April 3, 2020 02:49
mod 4 cross pollination front end set up instructions for Svelte

Cross-Poll Svelte w/ Svelte Router Front End Environment Set-Up

  • To make a Svelte playground with a template, use this repo and follow the instructions in it's readme. If you want to use Svelte Router with the template, make sure to do the other steps below
  1. Clone down the repo or navigate into the template you've made with the steps above
  2. From the root directory of the project, run npm install and then run npm install --save svelte-routing
  3. Make sure the scripts property of your package.json file looks like this (there is a bug with svelte-router that requires this):
"scripts": {
    "build": "rollup -c",
 "dev": "rollup -c -w",

Home Page

New Event Inputs:

  • event title
  • date/(time?) (mm/dd/yyyy)
  • time
  • mileage (number entered by user if they choose not to use starting/event location)
  • payment (number)
  • notes (string)

If phase 1 goes well, add these things in addition to manually-entered mileage:

REF365 - Ryan Allen, Noah Gambee, Harrison Levin, Melissa Robbins

What did we like about this week?

  • Our daily 8:45am standups!
  • Our workflow has been good so far, solid mix of pairing and working alone
  • Learning new technologies has been a fun challenge so far

What did we learn this week?

  • Svelte and making requests to a GraphQL endpoint
  • GraphQl
  • Start with a smaller MVP

Latitude's Vestboard API Information Documentation


URLs

Steps:

  • Through the Vestaboard web app, select the Developers page from the left hand nav menu.
  • Select Create New Installable and name it.
  • Once created, select Details and then Create API Credential. Pick the device you wish to authorize with the installable.

Latitude Digital Requests for CarePenguin Back-End Changes

FEEDBACK: use http://jsonpatch.com/ format when it makes sense.


Request #1: Need to add subscription to the sensor object returned from the location/${locationID}/data endpoint.

  • Currently: GET location/${locationID}/data returns an array of sensor objects with these 4 properties:

    [{"id": 163, "name": "New Sensor1", "particleId": "1E001F001847393035313138", "timezone": "America/Denver"}]
    
@nwgambee
nwgambee / cwp_call_response.md
Last active October 26, 2021 15:25
CP CWP Call + Response Requests

CarePenguin Customer Web Portal New Calls

Endpoint for a user to hit when they deactivate their own account from the CWP

Method: DELETE 
Path: /user/:user_id/delete (Nick has set this up, check swagger)
Content-Type: application/json
Body: {}

Responses:

  • 403 failed to deactivate
@nwgambee
nwgambee / cp_swp_requests.md
Last active November 5, 2021 18:02
CP SWP Call + Response Requests

CarePenguin Support Web Portal New Calls

Endpoint for an admin to hit when they deactivate an account from the SWP

Method: DELETE 
Path: /user/:user_id/delete (Nick has set this up for users to deactivate themselves already)
Content-Type: application/json
Body: {}

Responses:

  • 200 Success
[
{
"key": "how_likely_acquire",
"type": "radio",
"answers": [
{
"label": {
"en": "Own",
"es": ""
},
[
{
"key": "post_event_bronco_opinion",
"type": "radio",
"format": "large",
"number": 1,
"answers": [
{
"label": "I like Bronco much more",
"value": "I like Bronco much more"