d0387c7aa2
The client first requests stops from the TS server (`0.0.0.0:80`), then the path from the Dart server (`localhost:8001`). It will be trivial to move the TS logic to the Dart server since the Dart server is the one that parsed all that data, and it's anyway in a `JSON` file. There is a `server/GET_ROUTES.json` file, but it's not needed. I just included it for easier debugging. `server/GET_STOPS.json` includes both the stops and the routes, and the client does some (inefficient) work to re-organize it. The Dart server uses a basic A* implementation to sort find direct routes and routes with transfers. The A* logic is in `src/shared/lib/src/graph/graph.dart`. This file defines the state itself, and `package:a_star` on Pub.dev (mine) defines the algorithm. `src/shared/bin/path.dart` is the whole of the Dart server. TODO: - add unit tests - this PR breaks almost nothing, so there is duplicate work being done on the client and some unused logic - return a structured path object for the client to use as it wants. This PR just sends a well-formatted string
30 lines
487 B
YAML
30 lines
487 B
YAML
name: client
|
|
publish_to: 'none' # Remove this line if you wish to publish to pub.dev
|
|
|
|
version: 0.1.0+1
|
|
|
|
environment:
|
|
sdk: ^3.5.0
|
|
|
|
resolution: workspace
|
|
dependencies:
|
|
fixnum: ^1.1.1
|
|
csv: ^6.0.0
|
|
flutter:
|
|
sdk: flutter
|
|
go_router: ^14.2.7
|
|
google_maps_flutter: ^2.12.0
|
|
html: ^0.15.5
|
|
http: ^1.3.0
|
|
polyline_tools: ^0.0.2
|
|
web: ^1.1.1
|
|
shared:
|
|
path: ../shared
|
|
|
|
dev_dependencies:
|
|
dhttpd: ^4.1.0
|
|
flutter_test:
|
|
sdk: flutter
|
|
|
|
flutter:
|
|
uses-material-design: true
|