[M] API for Special Closures

[Dianadec]

Description:

This ticket is to make any api updates that are needed to support the functionality of a DUP admin user setting a special closure on a park and reflecting that on the public side of DUP.

Acceptance Criteria:

• [x] if a DUP admin user sets a special closure then that status shows on the public front end
  • [x] any text added to special closure can be shown on public side
  • [ ] book pass button is not available to user while park is in this status
  • [ ] toggling to this status greys out the passes required status
  • [x] dates when park is in this status is stored in database and can be reported on in the future

Development Checklist:

• [x] Based on the outcome of the finalized design, park objects are to have two new properties: hasSpecialClosure (bool) and specialClosureText (or whatever you want to call these properties). We may drop the hasSpecialClosure prop if we figure it is redundant.
• [x] Update existing parks with the new property(s)
• [x] Modify Park PUT/(POST?) to include considerations for the above new park property(s)

Dependencies

• Blocked by
• Blocking

Relevant documentation as reference

Definition of Ready

• [x] Acceptance criteria are included
• [ ] Wireframes are included (if applicable)
• [ ] Design / Solution is accepted by Product Owner (if applicable)
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] UI meets accessibility requirements
  • [ ] Unit tests are written
  • [ ] Work is traceable in GitHub
  • [ ] PR linked to ticket number
  • [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • [ ] Code is peer reviewed and has passed CI/CD tests
• QA:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Code is potentially shippable to the production environment
  • [ ] Functional features have been tested and passed by QA
  • [ ] UI components tested by designer
  • [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Reviewed and approved by Product Owner

Notes:

[Dianadec]

This card will be updated according to Cam's idea around an easier solution. @cameronpettit cc @Christopher-walsh22

[Christopher-walsh22]

To be inline with changes to the ADMIN TICKET the acceptance criteria has changed.

book pass button is not available to user while park is in this status toggling to this status greys out the passes required status

Are no longer required as that functionality is managed by the passes required status.

[jpeersoxd]

@manuji I had a look at the PUT request in dev tools and verified the new specialClosure and specialClosureText fields. Not sure if you wanted to do some Postman testing of this, so I'm leaving it in QA for now.

[manuji]

Verified that this feature is working fine from the FE. Moving to PO review.

[JLWade]

moving to done :)