This repository has been archived by the owner on Jan 18, 2022. It is now read-only.
Messages weren't flushed to the database when send.immediately is false #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g was set to false. I think it should honor the useFlushOnSave setting. I also added the possibility to configure it on the builder with flush(true/false).
|
Also added configurable mappings options. Your mail can now easily be stored in another datasource. |
|
For asynchronous.mail.disable=true in some cases AsynchronousMailMessage not stored in DB |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think it should honor the useFlushOnSave setting. I also added the possibility to configure it on the builder
with flush(true/false).
If you want to see the effect, simply change the send.immediately to false in the example project. The to fields aren't saved to the database.