Skip to content

Feature: follow resources#1784

Merged
oriolgual merged 7 commits intomasterfrom
feature/follow-resources
Sep 7, 2017
Merged

Feature: follow resources#1784
oriolgual merged 7 commits intomasterfrom
feature/follow-resources

Conversation

@mrcasals
Copy link
Copy Markdown
Contributor

@mrcasals mrcasals commented Aug 30, 2017

🎩 What? Why?

This PR lets users follow resources on Decidim and get notifications when an event occurs on these resources. To start, the only events published are:

  • Meeting update
  • Meeting is closed

So the users can only follow Meetings as of this PR.

This PR will receive other smaller PRs so the work is easier to review.

📌 Related Issues

@mrcasals mrcasals self-assigned this Aug 30, 2017
@ghost ghost added the in-progress label Aug 30, 2017
@mrcasals mrcasals changed the title Feature/follow resources Feature: follow resources Aug 30, 2017
@mrcasals mrcasals mentioned this pull request Aug 30, 2017
@codecov
Copy link
Copy Markdown

codecov bot commented Aug 30, 2017

Codecov Report

Merging #1784 into master will decrease coverage by 0.06%.
The diff coverage is 95.28%.

@@            Coverage Diff             @@
##           master    #1784      +/-   ##
==========================================
- Coverage   98.65%   98.58%   -0.07%     
==========================================
  Files        1077     1115      +38     
  Lines       24412    24980     +568     
==========================================
+ Hits        24083    24626     +543     
- Misses        329      354      +25

This was referenced Aug 31, 2017
@ghost ghost assigned beagleknight Sep 6, 2017
mrcasals and others added 7 commits September 7, 2017 10:26
* Add Follow entity

* Add Notification entity

* Add Followable concern
* Publish update/close meeting events

* Separate events from followable resources

* Fix factory
* Create a notification for each follower when event is triggered

* Make events dcide who will receive the notification

* Add basic NotificationEvent module

* Only create notifications if event_class supports them

* Add event classes
* Make meeting events support emails

* Send emails from events

* Add default values for event emails

* Fix specs

* Fix rubocop issues

* Customize email texts per event
* Add basic NotificationDashboard

* Rename notification fields

* Find participatory space manifest for processes and assemblies

* Add read_at field to notifications

* Notification titles i18n

* Simplify notifications layout

Remove unused pagination and filters

* Mark notifications as read from UI

* Add notifications link to user menu

* Destroy notifications on read

* Fix rubocop complaints

* Paginate notifications

* Mark all notifications as read

* Improve JS code

* Add tests for notification dashboard

* Fix ivar name
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Follow a meeting

3 participants