[Search Consolidation] Generate Kotlin bindings for search component in Application Services
Categories
(Firefox for Android :: Search, task)
Tracking
()
People
(Reporter: skhan, Assigned: skhan)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
|
||
Comment 1•6 months ago
|
||
|
|
||
Comment 2•6 months ago
|
||
Authored by https://github.com/sarah541
https://github.com/mozilla/application-services/commit/bf3729759ae8806e1731e72ad440ab48a232fe40
[main] Bug 1950993 - Generate Kotlin bindings for search component
|
||
Comment 3•6 months ago
|
||
Hi skhan! Could you please provide some steps in order to verify this bug? Thanks!
|
||
Comment 4•6 months ago
|
||
This issue cannot be verified by manual testing.
Removing the qe-verify+ flag.
If, however, Sarah can provide us some steps, please set back the flag.
Thank you!
I am not sure this is something QA can test but if some developer wants to
-
To test in application services, the best way is to verify if these directories are created.
components/search/Cargo.toml
uniffi.toml
src/Rust code here.
android/build.gradle
src/main/AndroidManifest.xml -
To test in Firefox Android codebase,
I was just able to test in on my end that any class in the search component , we are able to utilize it in AC/fenix. Basically that the import is working. For example : I cared about the SearchEngineSelector class in AS
Earlier I wasn’t able to import it in fenix/AC but now I am able to
i.e import org.mozilla.appservices.search.SearchEngineSelector no longer gives an error.
Description
•