Combining the place picker and the geocode UI address autocomplete

[langsmith]

Resolves #818 by combining the Place Picker and geocoding autocomplete UI functionalities together. Several folks in #818 have expressed interest in having this.

@mapbox/maps-android , what do you think about the code and UI so far?

[LukasPaczos]

Looks cool 👍 I'd add the searchbox to the toolbar and collapse the search results list when a record is clicked.

[langsmith]

Made a little progress on this today.

.includeSearch(false) leads to the instructional Choose a location toolbar text:

.includeSearch(true) places the autocomplete search UI widget in the toolbar area:

The next TODO is hiding the search UI dropdown when a location is selected.

[percula]

This is great! Any chance of this being merged by the 29th, when Google officially deprecates their PlacePicker?

[langsmith]

Ok, things are finally behaving. This is ready for some more review.

The results drop-down list appears (i.e. the SearchView height is lengthened) when:

• typing occurs in the search UI EditText. Can be either the first text entered in the EditText or typing to adjust existing text.
• focus switches on to the search UI EditText. This happens when someone taps on the EditText for the first time and the cursor starts blinking in the EditText field.

The results drop-down list disappears (i.e. the SearchView height is shortened) when:

• it's showing and the map is tapped on.
• a location in the results list is tapped on.
• there's text in the search UI EditText and then the X clear button is tapped.

[langsmith]

Ok, I fixed FAB behavior. This is ready for another round of review when you've got a chance and are in the mood.

[langsmith]

[zugaldia]

/cc: @vng

[vng]

/cc: @alexander-kulikovskii

[LukasPaczos]

When the bottom sheet is hidden, the margin on the FAB is 0, while it should be 16dp or so. Also, when the bottom sheet is extended, the attribution view ((i) icon) does not match the padding of the logo.

Not sure what material guidelines are, but this slight movement of both fabs up and down does not look right. More of a nit pick this one, we can ship regardless.

There seems to be a race condition when extending the keyboard on view inflation that doesn't adjust the bottom sheets padding/margin correctly. Probably the keyboard measurement is performed too soon? Ultimately, do we even need the sheet to be adjusted for the keyboard?

If there's no search history and the keyboard is closed, the search view is still extended with an empty background. The search box generally doesn't lose focus on back press, while it probably should.

Because the toolbar in search mode has round edges, it creates an unnatural gap between the status bar and toolbar.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions.