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

#162752831 Refactored notifications response #51

Merged
merged 1 commit into from
Jan 3, 2019

Conversation

rickynyairo
Copy link
Contributor

@rickynyairo rickynyairo commented Dec 19, 2018

What does this PR do

Changes the notifications response to include a resource url that points to where the user can locate the particular notification.
The
URL uses the frontend domain so that users will be directed to the frontend.

Any other information

The PR requires the following to be set in your backend environment variables

Screenshots

screenshot 2018-12-19 at 11 36 43

@rickynyairo rickynyairo changed the title [ch #162752831] Refactored notifications response #162752831 Refactored notifications response Dec 19, 2018
@coveralls
Copy link

coveralls commented Dec 19, 2018

Coverage Status

Coverage decreased (-0.1%) to 94.589% when pulling 2e6ec9d on ch-refactor-notifications-response-162752831 into 75d4eec on develop.

@rickynyairo rickynyairo force-pushed the ch-refactor-notifications-response-162752831 branch from 3e889ec to 87e31e7 Compare January 2, 2019 15:30
@rickynyairo rickynyairo force-pushed the ch-refactor-notifications-response-162752831 branch from 87e31e7 to 2e6ec9d Compare January 2, 2019 18:20
@proxiex proxiex merged commit 4cc31c4 into develop Jan 3, 2019
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.

7 participants