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

Notification userid #2848

Merged
merged 1 commit into from
Feb 11, 2025
Merged

Conversation

sleidig
Copy link
Member

@sleidig sleidig commented Feb 11, 2025

see #2847

Make userId available on NotificationConfig entity because replication-backend cannot have a placeholder in combination with normal text (yet)

i.e.
possible:

{
  "subject": "NotificationConfig",
  "action": "manage",
  "conditions": {
    "userId": "${user.id}"
  }
},

not supported in backend:

{
  "subject": "NotificationConfig",
  "action": "manage",
  "conditions": {
    "_id": "NotificationConfig:${user.id}"
  }
},

related to Aam-Digital/replication-backend#171

Copy link
Contributor

Deployed to https://pr-2848.aam-digital.net/

@sleidig sleidig changed the base branch from master to feat/1055_notifications-final February 11, 2025 17:35
@sleidig sleidig changed the base branch from feat/1055_notifications-final to master February 11, 2025 17:40
@sleidig sleidig changed the base branch from master to feat/1055_notifications-final February 11, 2025 17:40
@sleidig sleidig merged commit 6cd7edb into feat/1055_notifications-final Feb 11, 2025
13 of 14 checks passed
@sleidig sleidig deleted the notification-userid branch February 11, 2025 18:09
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.

NotificationConfig permission to edit only own needs account-id placeholder in permission/ability system
2 participants