-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Feat/expense split app #146
base: main
Are you sure you want to change the base?
Feat/expense split app #146
Conversation
@arnb-smnta kindly go through the naming convention we are following for FreeAPI we are not following camel casing in file names and routes. Also, let us know once the PR is ready for review. Thank you! |
@wajeshubham @jwala-anirudh Its ready for review |
Why is |
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.
Cannot delete yarn.lock
file from root
@jwala-anirudh please see my new pr and see if it isok |
Please address this |
I've checked and still cannot see the recovery of yarn.lock file here |
@wajeshubham I have addressed the naming problem i think and also the yarn.lock problem i figure it out I think @jwala-anirudh its added can u just let me know if both the problems are addressed properly ? |
Why are you regenerating the |
@jwala-anirudh i think it is done now can u confirm the yarn.lock file problem |
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.
@arnb-smnta Kindly go through the review comments. @jwala-anirudh kindly review the architecture and functionality implemented in this app and check if it is correct once the review comments are resolved. Thank you!
@jwala-anirudh this is the new postman api collection corected the changes suggested by shubham |
@wajeshubham commited the changes suggested by you just not deleted the route comments for my understanding ,I was thinking of deleting the route comments just before the final commit after all testing and approval has been done for merging will it be okay if I just leave the comments for now will surely delete before the final review |
@jwala-anirudh sir any update on this |
@wajeshubham @jwala-anirudh sir any update on this |
@arnb-smnta Please go through all the review comments and fix those. If you have any doubts regarding any comment, please reply to the comment. Thank you. |
@jwala-anirudh @wajeshubham any updates on this |
@jwala-anirudh @wajeshubham any updates on this |
@wajeshubham @jwala-anirudh I have resolved all the issues as stated and the API is working fine can you just go through the code if any modification is required or not |
Hey @jwala-anirudh @wajeshubham This is draft PR for review of models routes and aggregation pipelines and helper functions This is mostly a work in progress most of the controllers are not tested yet as reviewed by anirudh in his comment #127 I am uploading it for initial review I will be using socket io for emitting expense group events after testing of all the routes thoroughly as socket io and configs are already present in the project I will integrating it at the very end