summer rework roadmap

[bobheadxi]

want to get this project in a workable state by end this summer in a timely manner. will involve some pretty significant reworking. here's a tentative plan, based on my experience toying around with https://github.com/bobheadxi/timelines, which i'll make public after exams and update this ticket with specific examples (#164 (comment))

the goal is to beat nwhacks to their re-implementation of their application system, and to use it for fall recruitment as a LP showcase project

refactoring

• drop core-gateway model, drop all protobufs, and condense into a single backend
• drop REST API, use graphql. this will save a lot of time both clientside and serverside since there's a lot of codegen tooling around it both for Go and React, and less headache designing APIs
• drop custom users, leverage something like AWS Cognito
• drop any redundant code and close all relevant issues
• switch to a typescript+React frontend

features

TBD - probably a similar featureset to before, so most of the existing issues still stand. the vast majority of work will take place on 2 fronts, once I do all the backend refactoring which should be done by end of may:

• design - if we cant get one completed, we can say fuck it and leverage the wireframes + some UI framework
• frontend implementation everything
• backend implementation of queries - how to get insights, etc.

paging @Schemetrical, @gbvivian, @suujia, and anyone else interested

design

• https://docs.google.com/document/d/1EW2qNKCYPfZb8CCtHPHSntMyUOJomHNWxbLJ1bkSPj8/edit#

[bobheadxi]

not entirely - just remove some of the boilerplate in between. I don't expect much change in core (DB wrappers, etc) - it'll just be functions called directly, instead of procedure calls. The only exception is probably the user code

on the gateway side... there really isn't all that much stuff there 😋

[suujia]

When robs coding skills are growing at an exponential rate while this project is growing linearly

[bobheadxi]

made my repo public, some examples:

• graphql
  • bad schema
  • what using the generated code looks like
  • playground, sourcegraph playground
  • on the frontend (usage)

[bobheadxi]

https://docs.google.com/document/d/1EW2qNKCYPfZb8CCtHPHSntMyUOJomHNWxbLJ1bkSPj8/edit#