rusty_bikes

dz / codestudy / rusty_bikes

Summary

Code study for Rust Bikes project by Binh Robles

Node Tree

• client_README
  • fetch_ts
  • webdev/nanostores
  • make_api_request_when_data_changs
• server_README

Nodes

server_README
content	Server README
remarks	Binh: The server readme has my kinda polished up notes that I've been writing as I've been working on this, and the arch diagrams might give you a decent sense of where things are in the system before you start diving into the code.
hyperlink	https://github.com/binhrobles/rusty-bikes/blob/main/services/README.md

client_README
content	Client README
children	fetch_ts (FE <--> BE interface), webdev/nanostores (mentioned by Binh, "overkill using nanostores as event bus within my FE code"), make_api_request_when_data_changs
remarks	The client readme also has a nifty dependency graph that I found to be pretty useful in visualizing how the FE code works. If you're interested in the FE <--> BE interface, the file of note is the client/src/store/fetch.ts file, which handles all server communication. I kinda went overkill with using nanostores as an event bus within my FE code, but essentially it enables me to make an API request whenever any of the relevant data pieces change.
hyperlink	https://github.com/binhrobles/rusty-bikes/blob/main/client/README.md

fetch_ts
content	fetch ts file
parents	client_README
hyperlink	https://github.com/binhrobles/rusty-bikes/blob/main/client/src/store/fetch.ts

make_api_request_when_data_changs
content	Nanostores enables API requests to be made when any relevant data pieces change. lambda_handler rust backend that handles the API call
parents	client_README
remarks	paraphrased from Binh Binh: st defines the APIs that the Rust backend can serve and uses the graph and geojson modules to perform the routing / format the API response.
hyperlink	https://github.com/binhrobles/rusty-bikes/blob/main/services/src/bin/lambda-handler.rs