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

Feat(share): Add comfirmation email to creator after share was send. #731

Closed
wants to merge 4 commits into from

Conversation

GitNees
Copy link
Contributor

@GitNees GitNees commented Jan 3, 2025

Related to my own request.
Im very new to this and need to figure out a lot, I dont even know how to test it, but looks pretty straightforward.

If I need to do something else, let me know, just trying to add something instead of only requesting:

#714

Added mail confirmation to creator, this means you can now send a bigger share, leave PC and see in mail it was send. This will help to know atleast a mail was send, if creator receives no mail, it will probably not been send to receiver.
@GitNees
Copy link
Contributor Author

GitNees commented Jan 3, 2025

I dont even know what this mean:
system-tests Expected — Waiting for status to be reported
or what to do...

@GitNees GitNees changed the title Add comfirmation email to creator after share was send. Feat: Add comfirmation email to creator after share was send. Jan 4, 2025
@GitNees GitNees changed the title Feat: Add comfirmation email to creator after share was send. Feat(share): Add comfirmation email to creator after share was send. Jan 4, 2025
@stonith404
Copy link
Owner

system-tests Expected — Waiting for status to be reported

You can just ignore that. These are system tests that will run when I approve the pull requests. Adding a new email shouldn't effect the system tests.

Copy link
Owner

@stonith404 stonith404 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, thanks for your contribution.

First of all I would recommend to you to follow the contribution guide to setup the project locally. When the project runs locally you can easily test it.

Additionally, the subject and message should be customizable like the other emails. You can inspire yourself by looking at the other email sending functions. New configuration variables can be added in the backend/prisma/seed/config.seed.ts file. I would also suggest to add a configuration variable that allows the admin to decide whether this email should be sent or not because in my use case I don't want to get a confirmation email.

@GitNees
Copy link
Contributor Author

GitNees commented Jan 6, 2025

Thats going to be above my level i think... I like the idea to set a confirmation option on or off, but I would not have any idea where, Ill have a look in the code later if I can figure something out, else ill probably close it till someone else can make it happen...

But thx for the feedback!

@stonith404
Copy link
Owner

I'll close this for now. Feel free to create a new pull request when you want to work on it again.

@stonith404 stonith404 closed this Jan 21, 2025
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.

2 participants