GitLab

added initial action as a demonstration of sorts-- removes all special schedules for selected facilities

Issue 80 fix

Closes #80

See merge request srct/whats-open!39

- phone_number now is actually serialized
- test on prod because you only live once
- version bump

2.1 Release

Closes #72, #64, #65, #63, #37, #61, #62, #68, #70, and #67

See merge request srct/whats-open!38

- docs docs docs

Resolve "Adopt Django 2.0"

See merge request srct/whats-open!37

- woo

Closes #72

Resolve "Add 'Shown Tags' field and change tags to 'Hidden Tags'"

See merge request srct/whats-open!36

- tags are for search
- labels are for informative phrases
- classifiers are for choosing which site to display on (shopmason, sodoxo, etc.)

Closes #64

Adding phone number

See merge request srct/whats-open!35

- just some simple fixings to make py2 compat work

- CI was breaking because it would try and install 2.0

Resolve "Allow a schedule to become a normal schedule on a certain date"

See merge request !34

- only promote if it is active

- done via a toggle
- will happen automatically when the schedule comes into effect

Closes #65

- also reorder fields to group open and closing items

Add optional note field to Facility

See merge request srct/whats-open!33

- Allows you to send whatever text you want to clients
- Responsibility on admins once again

Closes #63

Support Facility logos to be served through the api

See merge request !32

- It's a URLField
- Depends on trusting the admins not to insert dirty images to be sent to clients
- pls

Closes #37

Default (x,y) position on admin map

See merge request !31

- yay finally

Closes #61

Add friendly building names attribute

See merge request srct/whats-open!30

- specify as abbreviation

Closes #62

Resolve "Special Schedules that do not expire"

See merge request !29

- by default, remove all schedules
- but of you click this button then this behavior will not happen

Closes #68

- by default, remove all schedules
- but of you click this button then this behavior will not happen

Alter valid_end and valid_start to use DateTime

See merge request !28

- in some silly scenarios, a schedule may come into effect on a date at a certain time
- this allows that to happen

Closes #70