inverted appointment order, implemented loading by date range
Signed-off-by: Stephan Richter <s.richter@srsoftware.de>
This commit is contained in:
@@ -147,7 +147,10 @@ public class ApiEndpoint extends PathHandler {
|
||||
return HttpError.of(400,"Count (count=%s) is not a number!", o);
|
||||
}
|
||||
|
||||
return db.list(startDate, null, count, offset).map(res -> filterByTags(res, tags));
|
||||
Result<LocalDateTime> end = parseDate(param.get(END));
|
||||
var endDate = (end == null) ? null: end.optional().orElse(null);
|
||||
|
||||
return db.list(startDate, endDate, count, offset).map(res -> filterByTags(res, tags));
|
||||
}
|
||||
|
||||
private Result<List<Appointment>> filterByTags(Result<List<Appointment>> res, List<String> tags) {
|
||||
|
||||
@@ -93,6 +93,7 @@ function fetchLastYear(){
|
||||
async function handleEvents(response){
|
||||
if (response.ok){
|
||||
var json = await response.json();
|
||||
json.reverse();
|
||||
json.forEach(addRow);
|
||||
updateTagVisibility();
|
||||
if (highlight){
|
||||
|
||||
Reference in New Issue
Block a user