Status Update
Comments
ad...@google.com <ad...@google.com> #2
I am not sure I understand the use case. how can the benchmark be code to real world scenario when it's not possible to do right now ? which scenario is it ?
In any case, since this would be for benchmarking, this would clearly not be available through the public DSL. We should find a semi-private way of doing this (maybe the private variant API object could offer that functionality for instance or a property).
le...@gmail.com <le...@gmail.com> #3
We want benchmarks to measure code after Progaurd / R8, but it's not possible to turn that on for androidTests in library modules at the moment (to my knowledge?)
Benchmarks are also a public facing thing, but we have a plugin to help configure gradle builds for our users, so if support for this ends up in a private API, we could try to keep those usages localized to our code perhaps.
Description
AppSearch module used: local-storage
AppSearch version used: 1.0.0-alpha03
Devices/Android versions reproduced on: n/a
When you encountered this bug:
The context for this issue is that, we found malformed data that entered the database and the only way to verify this at the moment is to query the database and output the results to the logcat.
Android Studio has a useful database inspector for Room-based dbs which I assumed would also include the AppSearch (local-storage) db.