The migration code fails when user_settings is non-empty
because it adds a non-nullable constraint before DML is applied.
This fixes that issue and adds a test case for that particular migration.
Signed-off-by: Adam Kunicki <kunickiaj@gmail.com>
The settings can be customized for each origin and each processor
individually. The default Web indicates notifications shown in the
Backstage UI. By default, if there are no settings saved in the
database, all notifications are enabled for all processors.
The origins will populate by time for each user as they receive the
first notification from that origin. Processors are shown as their own
columns.
Later, if it makes sense, allow users to also disable/enable
notifications based on notification topic.
Signed-off-by: Heikki Hellgren <heikki.hellgren@op.fi>
the broadcast notifications are returned with the same queries as user
notifications with only few exceptions in the store
Signed-off-by: Heikki Hellgren <heikki.hellgren@op.fi>
using same topic twice will restore existing notification in that topic
if any. this can be useful if you want to remind users about some
specific thing over time
Signed-off-by: Heikki Hellgren <heikki.hellgren@op.fi>
Fredrik Adelöw