-
Notifications
You must be signed in to change notification settings - Fork 35
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
DESK_REJECT added #1285
base: develop
Are you sure you want to change the base?
DESK_REJECT added #1285
Conversation
api/app/outcome/api.py
Outdated
event=event, | ||
user=user, | ||
) | ||
print("event_type::::::::", event.event_type) |
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.
"print" shouldn't be in the production codebase?
api/app/outcome/api.py
Outdated
user=user, | ||
) | ||
print("event_type::::::::", event.event_type) | ||
print("Type of event.event_type:::::::", type(event.event_type)) |
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.
"print" shouldn't be in the production codebase?
(please see comments above)
api/app/outcome/api.py
Outdated
event=event, | ||
user=user, | ||
) | ||
print("event_type::::::::", event.event_type) |
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.
"print" shouldn't be in the production codebase?
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.
Hi @upaq. Thanks for noticing these! Yes, it should not be in the production. I will remove it now.
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.
Cleaned up. I think there is no other print statement that would go in prod.
A DESK_REJECT status added, primarily for Journal events. To facilitate emails for this status, two new email templates added for journal desk reject and reject. A reason is also propagated to the email for desk_reject and reject, which is propogated through outcome services, therefore a new reason column is added in the outcome table. Finally, all migrations are performed.
Please let me know if there are any changes needed!