**background**
Blocks will need to have a defined beginning and end. Admins sometimes want to block for a short period of time (a time out) vs extended (ban).
**user story**
as an admin, I want to set a duration for a block so that I maintain the integrity of our projects
**requirements/acceptance criteria**
Given that an admin is creating a block, when they see the expiration field, then they should see a dropdown and be able to select a time interval
- Dropdown: Indefinite, 2 hours- Preset duration:: 1 Hour, 24 h4 Hours, 3 days8 Hours, 71 days, 14 days1 Week, 30 days1 Month, 90 days3 Months, 180 days6 Months, 365 days1 Year, Other time: select a Indefinite date and timete
- Other duration: num: 1-12, Hours, Days, Weeks, Months, Years
- Calendar picker: select a finite date and time
- Toggling between calendar and dropdown options should preserve the entry
- Expiration is required. An error state should be shown if it is not selected
- Expiration dates should always be in the future; selecting a day or time in the past should throw an error
-
Implement 'Expiration' field in Codex. This field will allow admins to select when a block should expire.
//
When a block is sitewide and the block is indefinite, the option "Hide username from edits and lists" needs to be enabled; otherwise, it is disabled. //
The block type field should look and feel as defined in [[ https://www.figma.com/file/3PthdmimQ8FiuhGIsLhmZi/Multiblock?type=design&node-id=853-19790&mode=design&t=M42UnSCtZKDoPhy7-0 | Figma file ]]