-
Notifications
You must be signed in to change notification settings - Fork 1
SAN-3947 - Set file size limits #1561
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
Conversation
Myztiq
commented
Apr 22, 2016
•
edited by thejsj
Loading
edited by thejsj
- Added logic to handle file too large errors
- @thejsj
- Reviewer 2
The latest push to PR-1561 is running on SAN-3947-file-size-limits-runnable-angular |
So the api is going to attempt to fetch the file, but then return an error? |
@Nathan219 Check this pr: CodeNow/api#1484 |
@@ -9,6 +9,11 @@ | |||
) | |||
p.p We're Sorry, but your file is in another castle… and that castle just blew up! 😱 | |||
|
|||
.blank-panel( | |||
ng-if = "!loading && hasError === 'tooLarge'" | |||
) |
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.
Would it be better to reuse the existing .blank-panel element and replace the text?
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.
If we did that'd result in having 3 ng-if's because we only want blank-panel to show if there is an error
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.
But it's a matter of preference, would you prefer I did that? @runnabro
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 was thinking that !loading && hasError
might cover it. I just thought it would be simpler. Do what you think is simpler.