Reserved keyword in dataclass about grand HOT 3 CLOSED

I agree. But perhaps this is a good moment to standardise the date? At the moment it is just a string. I prefer unix timestamps, and that's what I am usually using. But it is not readable by the eye. On the other hand, hardly anyone will read the trees by eye, I think.

And the naming: actually I see inconsistency in the naming. Sometimes I add the prefix "event_" to the fields, sometimes I don't. Probably, in general, there should not be such prefixes... But maybe not worth the effort to change it.

from grand.

@grand-oma @mjtueros @luckyjim @pmitra-astro @rameshkoirala @niess

from grand.

Thanks for your answer. I agree that it's the good time to standardise all dates and time fields and names !
I think unix timestamps are a good option (even if not readable by eyes, but it's not difficult to convert it when we want to see it). For naming, I think it's good practise to avoid reserved keywords (like date, time, etc...) and add a prefix makes easier to understand the meaning and not so complicated to do.

from grand.