-
Notifications
You must be signed in to change notification settings - Fork 8
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
adding a modal with project rejection #554 #574
base: master
Are you sure you want to change the base?
adding a modal with project rejection #554 #574
Conversation
not finished
@mboudet this one can be reviewed |
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.
No reason to commit this file
|
||
openRejectModal(project: any, user_uid: any) { |
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.
Any point in having user_uid? I'm not sure you actually use it anywhere?
if(this.rejectionReason) | ||
this.userService.notify(this.currentProject.owner, { | ||
subject: `: Project ${this.currentProject.id} creation rejected`, | ||
message: `The reason why your project was not accepted by one of our admins is the following: ${this.rejectionReason}`, | ||
send_copy_to_support: this.sendCopyToSupport | ||
}).subscribe( | ||
err => { | ||
console.log(('failed to send mail')); | ||
} | ||
); |
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 feel like this part should be done in one block in the 'reject_project' call (in the backend), instead of doing two separate api calls.
} | ||
res.end(); |
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.
Not need for this line, the res.send() above is sufficient
This PR resolve this issue : #554