Added support for new Route Search API #149
Open
+394
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary #146
/api/where/search/route.jsonusing SQLite FTS5 for full-text route search, matching OneBusAway’s route search spec.routes_ftsvirtual table with triggers to keep FTS data in sync and a rebuild to cover existing data.SearchRoutesByFullTextquery and GTFS manager helper that builds safe prefix queries and caps result size.input, checksmaxCount, and returns list + references consistent with existing/whereendpoints.modernc.org/sqliteto ensure FTS5 is available in tests/builds without native SQLite deps.Implementation Notes
routes_ftswith insert/update/delete triggers; rebuild inserted to backfill existing routes.SearchRoutesByFullText; manager helper constructs FTS-safe"term"*AND-joined queries with limits.internal/restapi/routes.go; uses existing validation/response helpers to match schema of other list endpoints.github.com/mattn/go-sqlite3withmodernc.org/sqlitefor FTS5 availability across environments.Testing
go test ./...