- General
-
Idées
0
À l'étude
API: Get only updated content
Hello,
currently i am trying to build a mobile app that uses the EB API.
I want to cache all content local so the user doesn't need to load all the data every time he starts the app. But do to this, I have to know what changes are done since th last update. At the moment I cannot pass any filter parameter to the API requests. I would like to use a parameter like "last_updated" or something similar.
Are there any plannings for such a filter?
Best regards,
Josef Biehler
currently i am trying to build a mobile app that uses the EB API.
I want to cache all content local so the user doesn't need to load all the data every time he starts the app. But do to this, I have to know what changes are done since th last update. At the moment I cannot pass any filter parameter to the API requests. I would like to use a parameter like "last_updated" or something similar.
Are there any plannings for such a filter?
Best regards,
Josef Biehler
Solution
Solution
À l'étude
There are no plans for such a filter, but it could be added easily. Which models / data records would you be doing a query like this on?
Out of interest, will this app be available to others, or only for internal use?
Out of interest, will this app be available to others, or only for internal use?
I think it is useful for the query to get the stories for a theme and for the query to get the acceptance-criterias.
The app is open source and hostet on github.
So it is available for all. But i don't know if i will publish it, on the app market.
The app is open source and hostet on github.
So it is available for all. But i don't know if i will publish it, on the app market.
Hi Josef
OK, one thing I thought about though is how you will deal with deleted stories. How do you propose dealing with that? It is possible we could perhaps return a list of deleted stories too with either a separate query or perhaps a simple JSON list within the same query. Your thoughts would be appreciated.
Matt
OK, one thing I thought about though is how you will deal with deleted stories. How do you propose dealing with that? It is possible we could perhaps return a list of deleted stories too with either a separate query or perhaps a simple JSON list within the same query. Your thoughts would be appreciated.
Matt
Your suggestion sounds nice.
I was thinking about how to implement a local history to give the user the possibility to revert deletions of stories/backlogs/etc. This would have never been able to be the best solution, because if the user uses more than one device, every device have its own local history.
So if you can deliver deleted ones, that sounds really nice.
How about introducing a new Flag for every object, called "deleted" or something similar.
With a filter argument ("includeDeleted") for that flag (default should be "false" for backward compatibility i think) you could deliver the deleted objects within the same query as you do at the moment.
Josef
I was thinking about how to implement a local history to give the user the possibility to revert deletions of stories/backlogs/etc. This would have never been able to be the best solution, because if the user uses more than one device, every device have its own local history.
So if you can deliver deleted ones, that sounds really nice.
How about introducing a new Flag for every object, called "deleted" or something similar.
With a filter argument ("includeDeleted") for that flag (default should be "false" for backward compatibility i think) you could deliver the deleted objects within the same query as you do at the moment.
Josef
Service d'assistance aux clients par UserEcho
Out of interest, will this app be available to others, or only for internal use?