Ramit
06/08/2022, 6:36 AM1) before_dataset_loaded
2) after_dataset_loaded
3) before_node_run
4) after_node_run
5) before_dataset_saved
6) after_dataset_saved
I'm wondering if there is any way to change it to work in the following order:
1) before_node_run
2) before_dataset_loaded
3) after_dataset_loaded
4) before_dataset_saved
5) after_dataset_saved
6) after_node_run
Essentially, I need to encapsulate all Dataset operations such that they happen within a given node's lifecycle, not the other way around. Any tips would be greatly appreciated 🙂antony.milne
06/08/2022, 8:36 AMnode
as an argument to the dataset loaded/saved hooks (but with the current ordering), would that help? It's something I've thought in the past would be useful, and if this is another example of a use case then there would be a bigger push for adding it.datajoely
06/08/2022, 8:54 AMRamit
06/08/2022, 4:01 PM