Use nested dataclass to preserve all information
What does this merge request do and why?
- Use nested dataclass to preserve all information
- Remove redundant
to_dict
methods on classes that do not interact with BQ table.
This MR enable us to write more information to BQ table. Now all the information are contained in the final dataclass, we can pick as much as we want to write to BQ tables.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Merge request checklist
-
I've ran the affected pipeline(s) to validate that nothing is broken. -
Tests added for new functionality. If not, please raise an issue to follow up. -
Documentation added/updated, if needed.
Edited by Tan Le