This commit is contained in:
@@ -6,13 +6,6 @@ WIFI change 5g channel to 52,56,60 and 2g channel to 8
|
||||
recheck before doing as it seems to vary, maybe someone else's is auto switching
|
||||
|
||||
|
||||
|
||||
todo: Are UTC filters really working properly?
|
||||
Check that a datafilter with dates incoming datetime ranges are either interpreted as UTC on route (from post formdata maybe, already know query params are NOT)
|
||||
or that at some point in the chain they are converted to UTC like metricmm is doing on filter query
|
||||
I'm seeing weirdness with the metrics that makes me think the server is not filtering in UTC but converting the incoming datetime / assuming local
|
||||
Make a date filterable record confirm it properly finds based on time
|
||||
|
||||
todo: server state has a "more" icon in menu inexplicably
|
||||
|
||||
|
||||
|
||||
@@ -963,14 +963,14 @@ function untokenizeListView(lvJson) {
|
||||
//AFTER DATE?
|
||||
if (filterDates.after) {
|
||||
reto.filter.items.push({
|
||||
op: ">=", //GreaterThanOrEqualTo
|
||||
op: ">", //was GreaterThanOrEqualTo but that doesn't make sense, it's only greater than was seeing wrong return data as relative date filter already adjusts for boundaries
|
||||
value: filterDates.after
|
||||
});
|
||||
}
|
||||
//BEFORE DATE?
|
||||
if (filterDates.before) {
|
||||
reto.filter.items.push({
|
||||
op: "<=", //LessThanOrEqualTo
|
||||
op: "<", //was LessThanOrEqualTo but see above for after ===-----^
|
||||
value: filterDates.before
|
||||
});
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user