Closed ddsnowboard closed 7 years ago
Specced in 6a58db5130ca4c07fd5407ea9fbf772aece0e3d6
Now I just have to implement it. Easy, right?
With respect to the issue of infinite loops in the return Json, I was thinking that I could have abbreviated versions of each model that don't have any foreign keys, just IDs, and and return those when they're part of other models. That could solve the problem. EDIT: Spec'd in dae4ada2260cbec202268fa1c782a3b5a522724d
Also I have to have a way to register something so the backend can send a push notification to the user when they get a trade. I don't know the right amount of coupling I should use for this, but I have to have something for it, and I can't use the auth system like I thought I could (although I don't know why I thought this, that was ridiculous).
I need to have some way to edit things. I don't know the best way to do this. I might just leave it until after this assignment is done because I can probably get away without it and it will probably be complicated. Still, if I want this to be actually reasonable, I need to do this.
Also, I should probably make Floor
s appear to know what Player
s are on them from the API.
Also, for the Java interface, I am going to have a subclass of each object called "AbbreviatedX". I'm not sure how to make GSON like it, but if I can get that, everything should act like how it should.
I want to make an Android app for this, and I need an API for that.
Trade
or aStockSuggestion
. Spec'd in 9a4631b