Releases: Amsterdam/signals-frontend
Releases · Amsterdam/signals-frontend
v1.7.0
Additions
- Allowing setting
type
in incident submission form for authenticated users - Allowing changing
type
in incident detail page
Fixes
- Main menu z-index problem where the global notification was above instead of below the menu
- Infinite loop on the users overview page when navigating from the overview to a detail page and back
- Font styling for heading throughout the application
Misc
- Refactor of Redux' connected components
v1.6.2
v1.6.1
v1.6.0
Fixes
- Serviceworker cache refresh is forced after a new deploy has been performed. Previously, the new serviceworker was waiting to be applied and didn't serve the new assets right after successful deploy.
- Error message that was shown when accessing
/instellingen/gebruikers
(or similar pages) as a logged out user. - Inactive categories weren't filtered out from the API's response
Features
- Department detail page
- Categories overview page
- Category detail page
- Contact detail filter option for incident overview page
Additions
useFetch
Hook that supportsGET
,POST
andPATCH
- Custom hooks for the
settings
module:useConfirmedCancel
: show a confirmation message when a form edit is canceleduseFetchResponseNotification
: renders a global notification and does a page redirect after a form has been submit
- User detail page comment field
- Node version notes to README
- Help text below priority radiobutton list in incident submission form, incident detail and incident split page
Changes
- Category retrieval has been removed from the
App
container
Misc
- Node dependencies updates to their latest minor or patch versions
- Test logs have been cleaned by providing components with the rights props in tests
DataView
component has been moved to another location in the tree
v1.5.0
Fixes
- Form footer button order in the filter form
- Redirect to overview page from the detail page after adding or patching a role
- White-screen when viewing clicking on a user row in the user detail page with sufficient permissions
- List of incidents not updating after an incident has been split
Changes
- Allow the
CheckboxList
component to render disabled checkboxes
Misc
- Replace public categories endpoint by its private counterpart
v1.4.1
v1.4.0
Fixes
- An incorrectly handled state in the filter form when the form was reset and the form was showing the options of a stored filter
- Temporary fix for handling stored filters where the
priority
field was originally a string where the application now expects a list of strings. This particular change needs to be reverted after the backend has migrated the stored filters data. - Incorrect box-shadow size below the main menu on smaller screens
Reverts
- Variable redirect after login
- Addition 'Kerstverlichting' to incident submission form
Additions
- The list of priorities has gotten another option: 'laag'
Changes
- The
priority
option in the filter form has been changed into a list of checkboxes where it was a list of radio buttons. - Order of the
priority
options
Misc
- Adjustments to the application header on smaller screens
v1.3.0
Fixes
- Resetting the filter form left checkboxes checked where they shouldn't. Has been fixed by moving the filter form's state into a reducer.
Additions
- Categories model saga for the new private categories endpoint (in preparation of removing the public endpoint from the incident submission form)
Misc
- Pingdom script has been removed since it wasn't used anymore
- Role page title changed based on adding or editing a role
- Text label change for cancel button in role form