Background:
We have to fetch for the sessions from the api so that 1. they can be validated with the user's token 2. only the user's sessions come up 3. this is a way of ensuring that the sessions are actually posting to the realtime api
There were a lot of necessary changes that created a web of problems but then a waterfall of solutions and now the code is closer to the real deal! We now have a file that has sites with latitude and longitude and this is used to cross reference any time the selected site of the current session needs to be accessed. However, the selected site is currently hardcoded to be tst. But that can easily be changed in the future : )
FEATURE: Fetch sessions from api
Background: We have to fetch for the sessions from the api so that 1. they can be validated with the user's token 2. only the user's sessions come up 3. this is a way of ensuring that the sessions are actually posting to the realtime api
There were a lot of necessary changes that created a web of problems but then a waterfall of solutions and now the code is closer to the real deal! We now have a file that has sites with latitude and longitude and this is used to cross reference any time the selected site of the current session needs to be accessed. However, the selected site is currently hardcoded to be
tst. But that can easily be changed in the future : )