This PR enables dynamic data function arguments to be parametrised by using vm.Parameter (parameter targets in a format: <target_component>.data_frame.<dynamic_data_argument>).
The focus of this PR is writing docs, unit tests, making the export_data action to take this type of parameter into account. So the refactoring changes in the /actions folder don't need to be reviewed in detail.
Comment out the following configuration inside vizro-core/hatch.toml in case you get a better idea of what happens when caching is enabled.
[x] @antonymilne and @petar-qb to write docs - @antonymilne has started this
[x] @petar-qb to do manual test with redis to check new functionality including passing arguments. Since you'll be familiar with what they look like now after testing this current PR, hopefully it'll be easy to check it all makes sense when we test in the following PR
[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":
I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
I have not referenced individuals, products or companies in any commits, directly or indirectly.
I have not added data or restricted code in any commits, directly or indirectly.
Description
Completing https://github.com/McK-Internal/vizro-internal/issues/753 Builds on #479 (step 1 of 2)
This PR enables dynamic data function arguments to be parametrised by using
vm.Parameter(parameter targets in a format:<target_component>.data_frame.<dynamic_data_argument>).The focus of this PR is writing docs, unit tests, making the export_data action to take this type of parameter into account. So the refactoring changes in the
/actionsfolder don't need to be reviewed in detail.Comment out the following configuration inside
vizro-core/hatch.tomlin case you get a better idea of what happens when caching is enabled.TODO
TestCacheWithArguments.test_timeout_expires_all-> A potential solution https://github.com/mckinsey/vizro/pull/497Screenshot
Notice
[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":