You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add support for the max_age parameter for views.populate_csv #581
The REST API supports passing a max_age parameter when querying view data to avoid hitting the cache when requesting the data for a view. Currently, the methodviews.populate_csv or the CSVRequestOptions class do not.
Is it on the roadmap to add that capability? There is this workaround, but native support would be interesting.
I made a change to the TSC library so maxage (maxAge as in API spec) parameter is used in PDFRequestOptions class, however I still receive the cached PDF, so I am not sure if this is relevant for the caching solution.
Generate PDF - this should come with the new data (updates cache for around 75% of time for me, which was better than users clicking in the Web UI). Not perfect but acceptable.
Activity
rookxyz commentedon Apr 14, 2020
The same should be added to view.populate_pdf.
ndolash commentedon Jun 25, 2020
@timothyvermeiren @rookxyz
I made a change to the TSC library so maxage (maxAge as in API spec) parameter is used in PDFRequestOptions class, however I still receive the cached PDF, so I am not sure if this is relevant for the caching solution.
I cannot even try different pagetype.
rookxyz commentedon Jun 25, 2020
To verify cache update I used the following test: