This repository has been archived by the owner on May 15, 2023. It is now read-only.
table suggestion for api #6
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
March 11, 2019 16:43
|
Perfect, this worked. Here is one schema: |
|
@i-walker here is your API: https://app.tum.de/Api/openingtimes |
|
@kordianbruck Nice!
/** @param loc = User.aroundUser() would be called by the client if no location is specified
* @param time = now() is also called from client // we may change that I am not sure which is faster right now
/
fun locationIsOpen(loc:Location, time:TIME= now()): Boolean
fun IsOpen(time:Time= now()): Collection<Location>()
// I don't even care if we use a HashMap :)
if you're familiar with Higher Kinded Types we can use a Kinds<Container, Location>
I am open for suggestions. |
|
@jacqueline8711 On the Server:
locally on the device:
local DB and offline capabilities
Updating the API and offline DB/ Cache// I am pretty open which strategy we choose, but as far as I am concerned @kordianbruck doesn't // want a local DB. Therefore a simple Cache on the device should be sufficient. The idea would be to specify for each information resource a crawling strategy. missing information & crawling methods
|
|
@i-walker we already have a local DB. The API calls are also cached. Please just add the API as is now. We can refactor it further down the line by creating individual issues for each of your suggestions. I just would like to get the new data loaded from the above API that I've linked as quick as possible in the first step. Excellent ideas, please open separate issues that further describe those plans. Ideally the User Story in the Android App would describe the benefit for the users. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I will add the sql file with the updated data in the 2. commit.