-
Notifications
You must be signed in to change notification settings - Fork 28.9k
Fix autocomplete options height #80187
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
Conversation
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat. If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. |
@justinmc let me know your thoughts on this PR would be happy to make the changes :) |
@shihaohong can you please review this PR |
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.
This PR would need tests to verify that the updated, intended behaviors are reflected.
Thanks, I will add the tests to support this PR |
@shihaohong I am not sure if I have to write tests in widgets/autocomplete_test.dart as well |
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.
@maheshmnj It looks like there is some unrelated changes caused by your IDE/code editor, that is causing the analyzer test to fail, you have to revert those changes, it is basicaly remove empty spaces (custom formats) added by your IDE/code editor.
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.
The tests are failing due to an improperly formatted test (see my comment).
For flutter_build, you don't have to worry about it. It represents the status of the current Flutter build (without this PR). We only allow PRs to be merged when it is green. If it's red, someone is working on it, and you can just wait for it to turn green.
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.
Some comments about the test file's formatting and the test setup and clarity.
The analyzer check is also failing:
It might be unrelated to your change, so maybe rebase your branch with the master branch and see if it resolved the error failure. |
Thank you so much for the detailed review @shihaohong |
@shihaohong I am not exactly sure why the Windows build_tests are failing looks like they are timing out. |
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.
LGTM
The windows tests seem to be unrelated to your change and is an infra failure (I think the related issue is #81837). We'll have to wait for it to be resolved before we can merge this PR |
sure thanks again for the review |
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.
LGTM
@shihaohong looks like #81837 is resolved. do I need to merge the latest master? In order for windowsbuild_tests_2_3 to pass |
@maheshmnj I think so |
This pull request is not suitable for automatic merging in its current state.
|
This pull request fixes the Autocomplete Widget's options height issue #79227 and adds a
maxOptionsHeight
property allowing user to configure the maximum height theoptionsViewBuilder
can take.Fixes #79227