Approx address and MakanHistory filtering bug#101
Merged
Prakhar896 merged 7 commits intomainfrom Aug 2, 2024
Merged
Conversation
Prakhar896
requested changes
Aug 1, 2024
Contributor
Prakhar896
left a comment
Prakhar896
left a comment
There was a problem hiding this comment.
Well-done, super minor changes needed here and there
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What was done in this PR
1.) Implemented adjustements to backend APIs to conform to updated flow of tapping on the host's address and coordinates for all
foodListingson frontend2.)
foodListingswill update their address and coordinates accordingly upon changing the address of the host3.) Fixed bug where MakanHistory did not filter the reservations correctly
4.) Updated
FoodListingmodel, renamedcoordinatestoapproxCoordinates(SENSITIVE)--END OF PR--