Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add app notifications #7725

Conversation

Radicalchaos-zz
Copy link

@Radicalchaos-zz Radicalchaos-zz commented Feb 26, 2018

This PR will add a symmetrical set of options for in-app notifications, as is currently available for email.

  • HAML form
  • User settings controller
  • Control in-app notifications conditionally

= t(".receive_app_notifications")
= form_for "user", url: edit_user_path, html: {method: :put} do |f|
= f.fields_for :email_preferences do |type|
#email_prefs

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Do not repeat id "#email_prefs" on the page
  • id attribute must be in lisp-case

@denschub
Copy link
Member

Thanks for working on that, @Radicalchaos! Being able to turn off notifications completely for different kinds of events would be super cool.

Please be aware that our current system for storing preferences is... not the nicest, and it may not even be easily possible to add preferences for notification types, as our current email notifications are currently implemented via the UserPreference table, which isn't really designed to handle anything else than emails. If you already worked out a solution, cool. If not, feel free to drop by our usual communication channels so we can discuss about potential solutions. :)

(linking this PR to the matching feature request, which is #7686)

@denschub
Copy link
Member

denschub commented Apr 2, 2018

Hey @Radicalchaos! Do you plan on continuing this work? Is there anything we can do to assist you here?

@denschub
Copy link
Member

After a team-internal discussion, let's go ahead and close this PR. There is a lot of work left to do, especially since this PR is a front-end only PR for now. The backend portion is the more complicated stuff, and the frontend has to be adjusted either way, so closing this won't get rid of much.

If someone is interested in working on this, feel free to pick up this PR and base your own work on the work being done here. We will eventually work on this feature, because we agree that this is important and we really want to have it ourselves. :)

@denschub denschub closed this Apr 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants