View Code? Open in Web Editor
NEW
A RESTful backend written in Rust using Iron and an assortment of other Rust libraries. It's a playground for testing different ideas related to Iron and Rust. Feel free to check it out!
License: Apache License 2.0
PLpgSQL 23.75%
Rust 76.25%
backlogrs's People
Contributors
Stargazers
Watchers
backlogrs's Issues
E.g. by fetching game length information from an API.
The readme should describe the project and how to set it up.
It currently returns an empty array making it appear that the user actually exists when reality it doesn't.
The constraint of only one game_id per entry per user needs to be expressed in a different manner as the current solution is plain wrong.
In order for DbConnection to work iron::AroundMiddleware needs to be imported.
Investigate if possible to reexport from lib crate to remove the need for a separate import.
Using the /api/user/:id endpoint the url /api/user/library is parsed thinking library is :id.
To remedy this check input query string and make sure it is a number.
For ergonomic's sake models should have methods (trait impls) that as much as possible automate the task of interacting with the database.
This is to simplify for clients accessing the datetime not having to manually parse the Rust-specific time format.
Any updates to an entry should be logged in the database including time the update was made. It's interesting to get a feel for how the playing is progressing time wise.