Create choices template to have all multi choice experience be the same
as radio select choices.
Moved notes and tags into advanced template in order to reduce the
amount of fields in a form for users. Given that these two fields are
usually a catch all for anything that is not in the core data model. it
is not garunteed that users will use them.
If a user does decide to use the fields we will store that selection in
localstorage so that they dont have to open it every time.
I put the javascript into the page section, as i seem to have had issues
with javascript blocks overriding each other.
In order to have more control and flexiability on how elements are
rendered create field set implementation.
every field set gets rendered in order, and uses the template specified.
This should probably be built into the metaclass of the form but i have
no idea how to do that.
While Feeding for is great, i think there is room to create optimised
forms for breast feeding and bottle feeding.
This is the first one a trimmed down form for bottle feeding
specifically
* Add `nap` field, remove `napping` field.
* Default `nap` property to NULL
* Update existing tests
* Format the code!!
* Allow `Sleep.nap` to be blank
* Migrate settings from `NAP_START_MIN` AND `NAP_START_MAX`
* Remove `active` class from boolean fields
* Correct test method name and user config
* Add forms test
* Use settings for Sleep nap model tests
* Update Tempus Dominus to v6 (WIP)
* Re-add calendar input prepend container
* Normalize setting of default date values
* Migrate to Bootstrap 5 (WIP)
* Remove deprecated card columns implementation from dashboard
* Update BS5 data props
* Use Masonry layout for dashboard cards (for now)
This doesn't seem particularly ideal so may need a more involved refactor
* Update styles for Bootstrap 5 deprecations
* Remove resolutions crap
* Refactor deprecated BS4 classes
* Update list table styles
* Refactor deprecated jumbotron class usages
* Update close button structure
* Add `v2` branch to standard CI workflows
This allows the custom tag widget to function normally in Baby Buddy's
frontend without breaking behaviors in the Django admin forms. The previous
setup would prevent the standard tag editor behavior from working in the
Django admin and give incorrect help text.