serlo/notification-mail-service

Issues

• chore: Refactor Dockerfile and make container smaller

  #88 opened a year ago by kulla
  0

• Fix e2e tests

  #83 opened a year ago by hugotiburtino
  1

• Mock API for local development

  #36 opened a year ago by hugotiburtino
  0

• Fix "yarn template"

  #89 opened a year ago by kulla
  0

• Add / check yarn settings in https://github.com/serlo/notification-mail-service

  #69 opened a year ago by eliflores
  0

• Set module type to ESM in https://github.com/serlo/notification-mail-service

  #67 opened a year ago by kulla
  0

• Pin tools in https://github.com/serlo/notification-mail-service

  #64 opened a year ago by eliflores
  0

• Update yarn to latest version in https://github.com/serlo/notification-mail-service

  #57 opened a year ago by kulla
  0

• Further Improvements

  #29 opened 2 years ago by hugotiburtino
  0

• Add pact tests

  #38 opened 2 years ago by hugotiburtino
  0

• Create Docker image

  #4 opened 2 years ago by hugotiburtino
  1

• Refactoring of the current main branch

  #32 opened 2 years ago by kulla
  0

• Optimize call to API

  #34 opened 2 years ago by kulla
  0

• Refactoring: Use fragments in get-notifications-query.ts

  #33 opened 2 years ago by kulla
  0

• Implement basic Notification Mail Service

  #1 opened 2 years ago by hugotiburtino
  1

• Follow up: complete basic implementation and apply best practices

  #5 opened 2 years ago by hugotiburtino
  1

• Send also discussions (like in legacy)

  #10 opened 2 years ago by MoeHome
  2

• Improve styling and wording of the email body (maybe use a template engine)

  #8 opened 2 years ago by MoeHome
  2

• Give more information about the entity, taxonomy term etc.

  #11 opened 2 years ago by MoeHome
  4

• Users not receiving notification email

  #27 opened 2 years ago by hugotiburtino
  2

• Add Sentry

  #23 opened 2 years ago by hugotiburtino
  0

• Refactor: Consistent database handle

  #9 opened 2 years ago by MoeHome
  2