Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

Any development on this @msyaojz
The lack of this feature is currently blocking me from release, so I may need to open a seperate PR for the same isssue soon.

This is probably not the approach we would want to take for this... I would imagine we would either make openDrawer return a Future that's also exposed on ScaffoldState, or maybe have a ValueListenable<bool> that reports the current state of each drawer, or some such. But it mostly depends on what the use cases are. I recommend going into more detail in one of the issues linked above about what exactly it is that you need this feature for so that we can come up with a more coherent design.

Another possible idea is exposing the Animation that represents the drawers sliding in and out.

(The problem with callbacks is that they wouldn't be usable in other contexts, e.g. you couldn't await one, or pass one to an AnimationBuilder, or the like.)

Because this implementation isn't really the best way of implementing this feature, we're going to close this pull request for now.

Since the CLA wasn't signed on this PR, I'm going to close it. We can't accept patches where the CLA hasn't been signed.

@msyaojz if you have the opportunity to sign the CLA, please don't hesitate to do so and open a new PR! Thanks!

This should be resolved by #67249