-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Email subscription improvements #1535
base: master
Are you sure you want to change the base?
Email subscription improvements #1535
Conversation
…e with optional parameters to modify how the body of the email gets constructed
… email-subscription-improvements
… email-subscription-improvements # Conflicts: # hapi-fhir-jpaserver-subscription/src/main/java/ca/uhn/fhir/jpa/subscription/module/interceptor/SubscriptionDebugLogInterceptor.java
…m getPayloadId to getResourceId)
This pull request introduces 2 alerts when merging e851830 into eb0a657 - view on LGTM.com new alerts:
|
Fixing LGTM errors about boxed boolean variable
… email-subscription-improvements � Conflicts: � hapi-fhir-jpaserver-subscription/src/main/java/ca/uhn/fhir/jpa/subscription/module/subscriber/ResourceDeliveryMessage.java � hapi-fhir-jpaserver-subscription/src/main/java/ca/uhn/fhir/jpa/subscription/module/subscriber/SubscriptionDeliveringRestHookSubscriber.java
This pull request fixes 1 alert when merging 4fd3c8d into c3c6796 - view on LGTM.com fixed alerts:
|
Hey @seanmcilvenna - The last CI faliure was as a result of a bug unrelated to your change that has been fixed. Can you merge master into your branch once more? |
…e. Otherwise, interceptors can't get the original resource to examine it.
This pull request fixes 1 alert when merging 578b9db into 995bda0 - view on LGTM.com fixed alerts:
|
Adding interceptors for SUBSCRIPTION_BEFORE_EMAIL_DELIVERY and SUBSCRIPTION_AFTER_EMAIL_DELIVERY
Adding enhancements to email subscriptions to accept a more-complex payload mime-type that includes mime-type options of:
For example: "application/fhir+xml;bodynarrative=true" or "application/fhir+json;bodytext=dGhpcyBpcyBhIHRlc3QgbWVzc2FnZQ=="
When bodynarrative or bodytext is indicated, the resource XML/JSON is added to the email body as an attachment (a second "part" in the multipart body).
These changes are backwards compatible with previous functionality, with the exception that it always creates a multipart message body, even when there is only a plain/simple/empty string for the message body that doesn't have any attachments.