-
Notifications
You must be signed in to change notification settings - Fork 23
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
refactor: tackle corner cases and change variable names for better readability #38
Conversation
…adability Signed-off-by: Yash <yash2010118@akgec.ac.in>
} => ({ | ||
success: 'Deploy Delete Succeed', | ||
error: `Oops! It looks like the application (${app}) hasn't been deployed yet. Please deploy it before you delete it.`, | ||
folderShouldntExist: `The folder shouldnt exist after deleting it.`, |
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.
remove these two newly added cases, as they are not required, as the response is for user not the developer.
Remove the logic for folderShouldntExist, appShouldntExist, as all the cases are handled properly.
Also Dont use multiple return statements.
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.
Hey ! Thanks for the review I really dont think the cases are being handled properly. for example when scaling it for future there may be cases when the system disconects or any other simultaneous processes may block the current proccesses. I think these cases will be need and thus multiple return statements are necessary. Let me know if there are any alternate thoughts you have to the same.
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 see we shouldnt send it to the user but we need to handle these cases at the backend side IMHO
@khareyash05 for me it seems correct, I do not understand what @Creatoon said respect to the error messages. Can you update the conflicts to make it work again with the latest changes? Once you do that I will merge your PR. |
Resolved the conflicts. Maybe we are unable to comprehend what @Creatoon wants to say. If there is something I might be missing. Let me know. Thanks @viferga |
I passed the CI and after my change of considering all warnings as errors (of the linter), your CI execution failed: Correct this linter issue and I will merge it. |
fixed. Kindly rerun the CI |
Done, sorry for the long wait |
@khareyash05 seems to be still failing. |
I am merging this and I will solve the issues by myself. |
Thanks @viferga . |
Signed-off-by: Yash yash2010118@akgec.ac.in
serveStatic