16 Commits (4c527c273a9861b78ccbd8d4592a1e10cd462e4b)

Author	SHA1	Message	Date
ulferts	bbf05016b4	prevent non work package notifications to leak via the API	3 years ago
Oliver Günther	b91faeac6a	Rename remainders of reason_ian to reason	3 years ago
Oliver Günther	e3913e61e4	Remove read_mail, reason_mail, reason_mail_digest	3 years ago
ulferts	b3b3b80cb9	eager loading for notifications and activities ... Associations that cannot be loaded via rails` eager loading are eager loaded by hand: * The 'data' association of journals * The 'predecessor' association of journals * The 'journable' association of journals * The 'resource' association of notifiations Since the notifications and the activities index api have a similar data structure, notifications can reuse the eager loading of activities. Does not include any optimization for the rendering of the details as of now since the structure of the details is still subject to change.	3 years ago
ulferts	80718153d7	adding reason filter to notifications api	3 years ago
ulferts	96c792c0c3	adding project filter to notifications api	3 years ago
ulferts	f0fb2fbbed	split up notification reason involved ... Differentiate between the receiver being assigned or accountable.	3 years ago
Oliver Günther	e5dec2dc31	Add notification group_by for projects with transformed keys	3 years ago
Oliver Günther	e9ac166593	Add notification api specs for grouping	3 years ago
Oliver Günther	ccfa29c728	Move license and copyright docs to root, fix names and references	3 years ago
ulferts	8dfba679a6	introduce resourceId and resourceType filter ... These filters in combination allow filtering notifications via the associated resource, e.g. a work package. When only using the id filter, due to the polymorphic association of the resource, it will not be guaranteed to only return the desired notifications. A different resource, e.g. a meeting might have the same id. But using the resourceType filter by itself also makes sense so that a client can fetch only notifications associated to a subset of resources, e.g. work packages.	3 years ago
ulferts	34467120c3	introduce resourceId and resourceType filter ... These filters in combination allow filtering notifications via the associated resource, e.g. a work package. When only using the id filter, due to the polymorphic association of the resource, it will not be guaranteed to only return the desired notifications. A different resource, e.g. a meeting might have the same id. But using the resourceType filter by itself also makes sense so that a client can fetch only notifications associated to a subset of resources, e.g. work packages.	3 years ago
Oliver Günther	31726649d4	[38062] Avoid sending notifications with no ian reason	3 years ago
Oliver Günther	351cc7f969	[38062] Avoid sending notifications with no ian reason	3 years ago
ulferts	75bb809ad6	Feature/1899 send daily email summaries (#9430) ... * email digests * use time for notification digest setting * safeguard against empty digest	3 years ago
ulferts	f8b28b300c	treat nil value as non false ... The default BooleanEquals filter treats null same as false. Because of that, notifications that are not meant for ian were displayed. The BooleanEqualsStrict filter only filters for false as expected so that the notifications are not displayed.	3 years ago
ulferts	261b0fa5c3	add bulk read/unread enpoint for notifications	3 years ago
Oliver Günther	9636a08988	[26688] In-app notifications (#9399) ... * Add bell icon to icon font * Add in app notification in top menu * Add fullscreen modal * Add notification modal and items * Style items * Toggle details of item * Mark all read * Add no results box * wip specification for event api * Add events table, query and index * Send out events from WP notification mailer job There we have the recipients present * Add cleanup job for older events with a setting * Hide bell notification when not logged * Add specs for events API index/show * Fix setting yml key * remove pry in event creation * Fix before hook in events API to after_validation * Fix polymorphic association raising exception for aggregated journals * Fix typo in read_ian * Fix yml entry for mentioned * Add read/unread post actions to event API and add specs * Wire up API to frontend * Fix order on events * Switch to unread in notification * Add event query * rename WPEventService * route wp mail sending over events * rename spec methods * author becomes watcher * correct message call signature * rename events to notifications * renname parameter to reflect notification nature * create author watcher for existing work packages * Merge unreadCount from store * Take a stab at polymorphic representers * Fix link generation in polymorphic resources For journals, no title is being generated however * Fix frontend model for context * Use timer for polling * add notification_setting data layer * Fix show resource spec * Fix duplicate class in notification bell item * Add minimal feature spec for notification * API for notification settings * Persist notifications * adapt work package notification creation to notification settings * extract notified_on_all * consolidate wp#recipients * concentrate wp notification in journal service * simplify methods * Remove unused patch endpoint * Add specs for rendering and parsing notification settings * Contract spec * Update service spec * adapt specs * Angular notifications frontend commit e29dced646 Author: Wieland Lindenthal <w.lindenthal@forkmerge.com> Date: Mon Jun 21 17:34:50 2021 +0200 Create Akita store and query for notification settings commit 1a45c26c1a Author: Wieland Lindenthal <w.lindenthal@forkmerge.com> Date: Mon Jun 21 11:09:25 2021 +0200 Remove tabs from notificaition settings page commit 0ea21e90c1 Author: Oliver Günther <mail@oliverguenther.de> Date: Sun Jun 20 21:55:48 2021 +0200 WIP in app settings * migrate notification data * add project visible filter to project query * Add inline-create and table display grouped by project * Add notifications under admin/users * Remove notifications partial * Rename notififcations store to user preferences store * Add setting for self_notified and hook that up to the backend * Add aria-label to table checkboxes * Restyle table and toolbar * replace remains of mail_notifications attribute * initialize notification settings for new user * adapt my_preferences references * reenable no self notified for documents * adapt specs * Avoid has_many :notifcation_settings Rails magically autosaves the user's preferences when the user gets saved, which somehow also tries to save the notfifications even when unchanged. This breaks some specs such as the avatar upload spec. As we can't update the assocation through rails anyway, just delegate to the user for reading instead. * Restore update method of notification settings * Restore update spec * fix spec syntax * lint scss * linting * Fix content_tag for bell icon * Add feature specs for notification settings * Disable ContentTag cop * use visible filter to get projects for notification The visible filter will reduce the project list down to the set of projects visible to the user provided as a parameter. This includes public projects. * test for actual mail sending * adapt me resource path this.apiV3Service.users.me changed its type in 0d6c0b6bc7 * Implement changed migration * Linting * Add actor to notification representer * Fix factory creating a duplicate WP journal * Add work packages loading and journal details to notification entry component * IAN basic facets, keep and expanded states. * Fix notification bell spec * Render body separately and add auto updating relative time * Add fixedTime title * Add actor to notification entry * Fix clicking links on work package and project * Tiny styling changes on entry row * Disable count in notification if larger than 99 (wont fit) * Introduce virtual scrolling to entry table * allow delaying & prevent mail sending if ain read Introduces a setting to delay mail sending after a journal aggregation time has expired. That way, users can confirm a notification in app. If they do before the delay expires, no mail is sent out additionally for that user. * consolidate notifications (in&out) into shared admin menu Co-authored-by: ulferts <jens.ulferts@googlemail.com> Co-authored-by: Wieland Lindenthal <w.lindenthal@forkmerge.com>	3 years ago