feat: Save attendees to DB #2300
Merged
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
liveHarshit
reviewed
Aug 23, 2019
| .nonNull() | ||
| .observe(viewLifecycleOwner, Observer { | ||
| if (it.isEmpty()) { | ||
| Toast.makeText(context, getString(R.string.error_fetching_attendees), Toast.LENGTH_SHORT).show() |
There was a problem hiding this comment.
How you're revalidating attendees form API?
I don't think it is necessary to revalidate attendees from API as it is not possible to update attendees after order is made. If we need to then it is still possible as in #2281 SwipeRefreshLayout is added to refresh order, which should also refresh attendees if both PRs got merged.
liveHarshit
previously approved these changes
Aug 23, 2019
liveHarshit
approved these changes
Aug 24, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes: #2299