This repository was archived by the owner on Mar 4, 2025. It is now read-only.
Feature/sup 2120 fix #557
Merged
Feature/sup 2120 fix #557
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -44,10 +44,13 @@ | |||
|
|
|||
| function activate() { | |||
| $scope.numImages = 0; | |||
| if (!$scope.challenge.isPrivate && $scope.challenge.userDetails.submissions && $scope.challenge.userDetails.submissions.length > 0) { | |||
| $scope.numImages = $scope.challenge.userDetails.submissions.filter(function(submission) { | |||
| if ($scope.challenge.userDetails.submissions && $scope.challenge.userDetails.submissions.length > 0) { | |||
There was a problem hiding this comment.
Will $scope.challenge.userDetails always exist? Or do we need to check that that exists as well?
There was a problem hiding this comment.
i'll add a check, thx
|
Just have the one comment, otherwise LGTM |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fyi @nlitwin this fixes an issue in prod, it's hard to replicate in dev, so if you're testing locally, just make sure the code looks good and nothing is broken