-
Notifications
You must be signed in to change notification settings - Fork 551
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: Notification Fragment #1622
Conversation
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.
When you submit a WIP PR, it helps if you could point out where you are having problems
34016ee
to
ac2bf16
Compare
@iamareebjamal @nikit19 Need your suggestion on following points
|
Don't delete notifications, just mark read. Show notification button always, in case not logged in we'll show local notifications (planned later) If there are no local notifications, we'll show There'll be a button to mark all notifications as read since there is no notification target as of now We'll use Html.fromHtml for now. The backend structure for notification will change
|
7c00571
to
7145772
Compare
todo: @iamareebjamal @nikit19 please review |
0546929
to
8ec7b5e
Compare
@iamareebjamal @liveHarshit @nikit19 please review |
PRF |
Sorry, what? |
Peer review first 😅 |
setToolbar(activity, getString(R.string.title_notifications), true) | ||
setHasOptionsMenu(true) | ||
|
||
if (notificationViewModel.isLoggedIn()) { |
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.
Why are you checking again for authentication?
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.
To prevent the api call if not logged in.
then in onStart, redirect to login.
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 onCreateView is always called after onStart, so can't you remove onStart here?
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.
bro no, onStart is called after onActivityCreated
https://developer.android.com/guide/components/fragments
@aman210697 if you're still working on this please resolve conflicts and if not I'll do it |
Conflicts are not big, so I'll update it before the approval. |
I was talking about resolving the conflicts |
Resolved conflicts, and updated to RxKotlin & RxExtensions.. Please review |
may I fork this PR and finish it by resolving conflicts? |
If you haven't started yet, I'll resolve.. |
641334b
to
40b7aea
Compare
@aman210697 oh great |
resolve conflicts and updated navigation ACTIONS API |
Part of #1617
Changes: fragment setup