Open stephenholleran opened 1 year ago
@stephenholleran I don't see why lidar_config.date_from
and by extension the date_from
in other tables should be optional. Plus +1 from me to make it required.
@stephenholleran and @abohara I think that if you don't make it required, then there is no way to track to what period that configuration is associated to.
@kersting Agreed
@stephenholleran Can we close ?
Hi @abohara, @kersting,
I think we are all agreed to make it required.
@stephenholleran Can we close ?
We won't close this issue as we now have to implement it. We will use this issue to track it in the kanban board.
This will be a breaking change so I'll mark this as a version 2.0 release.
@stephenholleran let me know if I can help either with the implementation or with the review (knowing that I need to do some implementation in other parts of the code).
From a pull request comment has sparked a review of this. https://github.com/IEA-Task-43/digital_wra_data_standard/pull/201#issuecomment-1404332701
Should the lidar_config.date_from property by required? It is currently optional.