Skip to content
This repository has been archived by the owner on Mar 23, 2022. It is now read-only.

Email subscription management #32

Closed
4 tasks done
RaenonX opened this issue Jan 8, 2022 · 0 comments · Fixed by #40
Closed
4 tasks done

Email subscription management #32

RaenonX opened this issue Jan 8, 2022 · 0 comments · Fixed by #40
Assignees
Labels

Comments

@RaenonX
Copy link
Member

RaenonX commented Jan 8, 2022

The data structure should be something like this:

{
  key: {
    category: "post",
    type: "quest",
    id: 33,
  },
  recipients: [
    "[email protected]",
    "[email protected]"
  ]
}

key should be a type so that it can be either translate to text for the front-end to display in UI.

Also, there should be a few constant keys for the special cases below:

  • All quest post
  • All analysis post
  • All misc post
  • All tier notes
  • Site announcement

Event binding

  • Post publish (global only)
  • Post edit (global, individual)
  • Tier publish (global only)
  • Tier edit (global, individual)
@RaenonX RaenonX self-assigned this Jan 8, 2022
RaenonX added a commit that referenced this issue Jan 16, 2022
RaenonX added a commit that referenced this issue Jan 17, 2022
RaenonX added a commit that referenced this issue Jan 17, 2022
@RaenonX RaenonX closed this as completed Jan 17, 2022
RaenonX added a commit that referenced this issue Jan 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant