-
-
Notifications
You must be signed in to change notification settings - Fork 22
feat: Implement optional email results #46
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
Conversation
|
The changes look good; I will review this as soon as I can. Thanks! |
hpacleb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updating the README file on how to use this optional function would be appreciated
Co-authored-by: Harvey Christian Pacleb <kimpacleb@gmail.com>
|
Kudos, SonarCloud Quality Gate passed!
|
|
@hpacleb missing period suggestion merged. Do you approve this PR? |
hpacleb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll just add the filename changes in another PR so this can be merged.
|
I'm going to add my 2 cents into this PR, I think users may want to customize the email template sent per datatable and not a generic one. But not really sure. |








I think this can be useful when export takes too long.
There is an optional email-to prop you can add to your button if you want the job to email the report once it's done.