Skip to content
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

Fix part of #5284: Revert "Fix #5266: Call setUpDrawer( ) directly if binding already initialized" #5285

Merged
merged 1 commit into from
Dec 23, 2023

Conversation

BenHenning
Copy link
Member

@BenHenning BenHenning commented Dec 23, 2023

Fixes part of #5284

Reverts #5276 as part of preparing to revert #5191.

Note that this reintroduces #5266 but that should stay fixed once #5191 is reverted.

This should be a clean revert.

@BenHenning
Copy link
Member Author

@adhiamboperes PTAL with urgency. This needs to get merged before we can revert the PR that's causing the problem, then both need to be cherry-picked into the release branch to unblock the release (which we need to get out ASAP since 0.11 expires on Dec 31).

@BenHenning BenHenning enabled auto-merge (squash) December 23, 2023 06:12
Copy link
Collaborator

@adhiamboperes adhiamboperes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving this since it is a clean revert.

@BenHenning BenHenning merged commit 31dfd2a into develop Dec 23, 2023
37 checks passed
@BenHenning BenHenning deleted the revert-5276-fix/nav-drawer branch December 23, 2023 07:55
BenHenning added a commit that referenced this pull request Dec 23, 2023
… binding already initialized" (#5285)

Fixes part of #5284

Reverts #5276 as part of preparing to revert #5191.

Note that this reintroduces #5266 but that should stay fixed once #5191
is reverted.
BenHenning added a commit that referenced this pull request Dec 23, 2023
## Explanation
This fixes #5284 for the upcoming 0.12 release by cherry-picking #5285
and #5287 into the release branch.

Both cherry-picks happened cleanly, so the review is expected to be
straightforward.

## Essential Checklist
- [ ] ~The PR title and explanation each start with "Fix #bugnum: " (If
this PR fixes part of an issue, prefix the title with "Fix part of
#bugnum: ...".)~
- [x] Any changes to
[scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets)
files have their rationale included in the PR explanation.
- [x] The PR follows the [style
guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide).
- [x] The PR does not contain any unnecessary code changes from Android
Studio
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)).
- [x] The PR is made from a branch that's **not** called "develop" and
is up-to-date with "develop".
- [x] The PR is **assigned** to the appropriate reviewers
([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)).

## For UI-specific PRs only
See corresponding cherry-picks and original PRs for references on what
reverted behavior is being checked in within this PR.

---------

Co-authored-by: Adhiambo Peres <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants