Description
/api/tree queries for the latest checkout for each tree. By default, it filters by checkouts in the last 7 days. However, this operation is really fast now (queries a pre-computed table), and there should be no reason to have this limit by default.
Related to this, there is a misagreement between the API and the dashboard here:
- API default is
interval_in_days=7 (as mentioned above)
- The dashboard root
/ redirects to /tree?i=7 and queries with interval_in_days=7 (not present in production)
- Dashboard
/tree queries with interval_in_days=30
Proposed solution
Therefore, I suggest:
- Keep
interval_in_days as optional, but do not filter if unset
- Make
/ redirect to /tree without hardcoded parameters
- Make
/tree query with interval_in_days unset by default
- Alternatively, grab the default directly from the backend
Description
/api/treequeries for the latest checkout for each tree. By default, it filters by checkouts in the last 7 days. However, this operation is really fast now (queries a pre-computed table), and there should be no reason to have this limit by default.Related to this, there is a misagreement between the API and the dashboard here:
interval_in_days=7(as mentioned above)/redirects to/tree?i=7and queries withinterval_in_days=7(not present in production)/treequeries withinterval_in_days=30Proposed solution
Therefore, I suggest:
interval_in_daysas optional, but do not filter if unset/redirect to/treewithout hardcoded parameters/treequery withinterval_in_daysunset by default