-
Notifications
You must be signed in to change notification settings - Fork 33
Request Hooks #65
Comments
Hi, |
This was released in #75 |
It seems that certain types of responses do not trigger
I am currently using fetch-intercept to provide custom loading indicators and I was hoping I could switch to custom Dash hooks but it's not possible due to issues describved above. Separately, it'd be nice if the hooks provided access to the actual Fetch request / response objects to inspect or modify.. I'll have to stick with |
Please make an issue for the problems you've encountered at https://github.com/plotly/dash/issues This repo is obsolete, the renderer has been merged into the main dash repo. |
The API requests that Dash's front-end makes should be configurable. In order to make them configurable, we will need to do the following things:
dash-renderer
) a standalone library that can be initialized and invoked from other librariesdash-renderer
to take a set of config input parametersrequest_pre
andrequest_post
parameter that will be called before and after HTTP requests with the entire request and response objects. This will enable the developer to transform the data before and after network requests.Example:
So, the hooks are only the network requests. In the code, this would fit in here:
dash-renderer/src/actions/index.js
Lines 447 to 455 in 70bb93e
Note that in order for users to supply their own arguments, I believe they would need to provide their own instance of
dash_renderer
by overriding the index file (as discussed here: plotly/dash#265)The text was updated successfully, but these errors were encountered: