Hanne Moa
Hanne Moa
I think you can combine this one and #757 and toggle_notification_profiles into a single command. "list" is incompatible with the others, it might even be the fallback if there are...
I found [sphinxcontrib-openapi](https://pypi.org/project/sphinxcontrib-openapi/), not tested.
Our schema needs to be improved a little, the "spectacular" management command has some complaints, I'll open a new issue.
- [x] Configure - [x] Set up to work with notifications - [ ] Set up to work in docker
I will test if changing the end-time time to be independent of the start_time, and changing how events are looked up timestamp-wise is sufficient to solve this.
I think it is easier that in the backend, we do not have timeslots (time recurrences) that go past midnight, but that one notificationprofile can have more than one timerecurrence...
The "admin"?-field would be read-only and optional. That it is **set** (to an url) means "make and show an admin-link in the frontend". "admin-url"? "admin-link"? Discuss.
See https://github.com/Uninett/Argus-frontend/issues/537
Actually, for bulk-events it makes more sense to have a method on the queryset, and when you have that method, it is trivial to also use it for single events...