will keep data for the future as given by that masjid if that data is available (they can decide how long in future time they want to keep the data of)
if not, just show that data is not available... in that case the masjid will have to provide data regularly when namaz times are updated
we can even send notification to update the timings if they forget to do so
[ ] create issue for plan how to implement this
how should we maintain special namaz timings? (jummah/multiple jamath for jummah/eid/janaza)
there will be two types of masjid
where masjid enters namaz timings preemptively
that way, we will have data of namaz for months down the line, which will be datetime (not just time as per current implementation)
where masjid enters namaz regularly
this way, masjid will update data for next day regularly
issue with this is that, it is possible that masjid might forget to update data, in that case we will simply show the next namaz as per some defined sequence, and show unavailable time, as we dont have data to say if that namaz is over.
[ ] create issues:
[ ] create task for the rework, and plan in it
[ ] update the schema as per new design (maintain datetime for each individual jamaat instead of just time)
[ ] update function to return namaz for the current day, or specified day/month depend on what the frontend need
Points Discussed
how should we maintain future namaz timings?
how should we maintain special namaz timings? (jummah/multiple jamath for jummah/eid/janaza)