bigmike36c

Thanks for correcting this so quickly! In my mind, if a user only selects a single date, then the user expects the date range to extend from the start date...

Makes sense to me. Could the callback just trigger with `"selected_date"` as a string instead of a list? This would make it easy to handle both single date and range...

Unfortunately, each gateway usually has its own [API definition](https://www.gravitee.io/blog/gravitee-api-definitions) since they all have different features around how they proxy, apply policies, create plans, etc. The actual APIs can adhere to...

Understood @rangav, thanks for all your work on this extension!

Should a new issue be opened up for the caching issue [detailed here](https://community.plotly.com/t/introducing-dash-pages-a-dash-2-x-feature-preview/57775/89?u=bigmike)? >Are there plans to integrate a solution to accessing the cache in callbacks outside the app.py file?...

Just to add to this, the same issue occurs with the dashboard engine for enterprise users. The workaround is easy enough by simply registering the dashboard engine page and declaring...