View Single Post
  #29   Spotlight this post!  
Unread 09-10-2014, 14:04
plnyyanks's Avatar
plnyyanks plnyyanks is online now
Data wins arguments.
AKA: Phil Lopreiato
FRC #1124 (The ÜberBots), FRC #2900 (The Mighty Penguins)
Team Role: College Student
 
Join Date: Apr 2010
Rookie Year: 2010
Location: NYC/Washington, DC
Posts: 1,114
plnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond reputeplnyyanks has a reputation beyond repute
Re: [FRC Blog] FRC Community Tools Developers Conference for FMS API

I'm pretty impressed with what's up so far. It seems the spec covers all the data that I could feasibly want (and more!).

There's really only two feature requests I can think of (which I'll put up on the tracker at some point):
- It would be nice to have a single endpoint to get all of an event's matches, with score data when available. Currently, it seems like I'd have to do a request to get the event schedule and then do a second request for the results and overlay the two. It shouldn't be too bad to have an endpoint just like the results one, but returns all matches and nulls out the scores for the unplayed ones.
- Push notifications would be awesome. But I understand those aren't a high priority at the beginning. Just keep them in mind for later while designing the system
__________________
Phil Lopreiato - "It's a hardware problem"
Team 1124 (2010 - 2013), Team 1418 (2014), Team 2900 (2016)
FRC Notebook The Blue Alliance for Android
Reply With Quote