-
Notifications
You must be signed in to change notification settings - Fork 212
Notification Backend Integration: All competitors should get challenge spec modified notification #4104
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
Comments
cc @macs054 |
{ As I checked the response of corresponding API /v4/challenges/30055753/resources , 'dan_developer' is not coming in 'submitter'. |
@sushilshinde @dushyantb , for reference please see #4055 (comment) dan_developer is a registered to the specific contest, but the corresponding api call does not return that user. |
@SathyaJayabal as checked randomly on prod for API v4/challenges/{challenge-id}/resources , getting correct data. So could be data syncing issue at DEV. Lets test it on Beta. Hopefully it should work there. |
closing this as spec modified notification is not in scope now |
At present only submitters get the challenge spec modified notification. All members registered to te challenge must get the challenge spec modified notification.
The text was updated successfully, but these errors were encountered: