Frontend and backend do not agree on how to define a timeslot/timerecurrence

[hmpf]

1. Week day number is different:
   • Back-end uses iso week day numbering, with Monday = 1, Sunday = 7.
   • Front end uses Monday = 0, Sunday = 6. The front-end sending in a 0 leads to a 400 Bad Request-error.
2. What goes in TimeRecurrene.days is different:
   • Back-end expects a string of comma-separated integers
   • Front-end send a single integer, and interprets a string of comma-separated integers as the first integer. For backend 1,2,3,4,5,6,7, front-end sees 1 (Tuesday).

Backend stores all the days as it does in order to make the admin prettier I suspect.

Conclusion: array of integers wins, frontend must be updated.

[lunkwill42]

ISO week day numbering throughout the system gets my 👍

[hmpf]

Uninett/Argus-frontend#114 seems to solve point 1.

[lunkwill42]

I really did have issues grasping how this was supposed to work in the frontend, and now I understand it's because of this issue. I want to make a timeslot that defines the period 8-16 every weekday, but I find myself completely unable to do so from the frontend. From the backend's Admin interface, it's no problem, however.

I find the array storage model for the backend just fine. What is missing is for the frontend to support multiple days per recurrence, and we need this in time for version 1.0

[hmpf]

Closed by Uninett/Argus-frontend#155