-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Migrated PostSettingsInputDialogFragment
to ViewBinding
#20941
Migrated PostSettingsInputDialogFragment
to ViewBinding
#20941
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.
dc5b518
to
8528c20
Compare
3c62fbf
to
57cfb46
Compare
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.
👋 @neeldoshii !
Thank you so much for your contribution to JP/WPAndroid with this PR! 🥇
I have reviewed and tested this PR as per the instructions, along with triggering CI on it via a draft PR, which I just pushed on the main repo, everything works as expected, good job! 🌟
I have left couple of suggestions (💡) for you to consider. I am not going to approve this PR, but also, I don't want to block it, thus I'll just add a comment review. I am NOT going to merge this PR yet to give you some time to apply any of my suggestions.
WordPress/src/main/java/org/wordpress/android/ui/posts/PostSettingsInputDialogFragment.java
Outdated
Show resolved
Hide resolved
WordPress/src/main/java/org/wordpress/android/ui/posts/PostSettingsInputDialogFragment.java
Outdated
Show resolved
Hide resolved
fb445cc
to
0c09e9e
Compare
WordPress/src/main/java/org/wordpress/android/ui/posts/PostSettingsInputDialogFragment.java
Outdated
Show resolved
Hide resolved
@@ -94,34 +93,32 @@ public void onDismiss(DialogInterface dialog) { | |||
public Dialog onCreateDialog(Bundle savedInstanceState) { | |||
AlertDialog.Builder builder = | |||
new MaterialAlertDialogBuilder(new ContextThemeWrapper(getActivity(), R.style.PostSettingsTheme)); | |||
LayoutInflater layoutInflater = getActivity().getLayoutInflater(); | |||
LayoutInflater layoutInflater = requireActivity().getLayoutInflater(); |
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.
Minor (🔍): Although this change is perfectly valid, consider avoid adding an unrelated change on a single commit. If you need to make this change, add a separate targeted commit on top of the main set of commits on a PR. Then, explaining the reasoning behind that change, even maybe group other such changes to make this change more impactful. How does this sound? 🙏
PS: No need for you to do anything here, this is just for educational purposes only.
Another tip from my side @neeldoshii , when you update your PR, enter into the habit of merging your changes with the latest change from Also, this way, you are making sure that new changes from Does that make sense to you? 😊 FYI: As you can understand, uninstalling and installing the app, then trying to login before testing such small changes can reduce a developer's productivity while reviewing a PR. |
Sure @ParaskP7, I understand. 👍 Previously, I was rebasing and squashing commits to keep the commit history clean and make it easier to revert changes if needed. However, I see your point about the difficulties it creates for reviewing and CI processes. From now on, I'll avoid rebasing after a PR is open and will add any changes as separate commits instead. Thanks for the guidance! 🙏
Understood! 👍 While merging the branch to upstream to the recent changes. I messed up which caused pushing the changes of commits behind from upstream. Can I perform git reset and force push now to clean this? What do you think is.better to fix this now? |
👋 @neeldoshii and thanks for being so cooperative! 🙏
Yes, no worries, please start over with a clean set. 👍 |
19499d6
to
d73aa4d
Compare
d73aa4d
to
3400278
Compare
Quality Gate passedIssues Measures |
👋 @neeldoshii !
I am still waiting for you on that, correct? 🤔 |
Hi @ParaskP7, I already did. Ready for review! |
Awesome @neeldoshii , thanks for the heads-up, will do the review asap! 👍 |
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.
👋 @neeldoshii !
Looking at your updates I am not seeing you applying at least this suggestion of mine, changing mBinding
to binding
. Unfortuantely, I can't merge this as it is breaking our coding guidelines in general. Can you deal with it please? 🙏
Hi @ParaskP7, nice catch thanks. I have updated the requested changes. |
Thanks @neeldoshii , will do the review asap! 👍 |
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.
🎉 @neeldoshii , everything is looking good, your second contribution to JP/WPAndroid is about to become history and soon merged into trunk
, thanks so much for this work! 🥇
Description
This pull request migrates the
AddCategoryFragment
to use ViewBinding, improving type safety and eliminating the need for findViewById calls.Fixes
findViewById
withViewBinding
#19180Screenshots/ Video
PostSettingsInputDialogFragment.webm
Steps to reproduce
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.Testing Checklist (strike-out the not-applying and unnecessary ones):