You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a reason to add some addtional logging messages, and I found the Log.e() and friends in the MainActivity class, but neither javadoc or code are attached so I'm pretty much guessing at the API. Specifically, the TAG.
This also hampers other grokking of the API, since I can't just hover or command-click on a method to see what it does. For example, I can't click through to see what methods there are on Manager or what overloads of getDatabase() may exist.
I'm not sure how hard it is, but it'd be a useful enhancement to have the javadoc or sources attached. I know this follows the android.util.Log class, but since it's pointing to our own com.couchbase.lite.util, it's up to us to link the javadoc.
Perhaps this is actually a bug? I don't actually see a good reason for us to be using a Couchbase extended class for logging in a sample app over the canonical logging methods.
The text was updated successfully, but these errors were encountered:
I had a reason to add some addtional logging messages, and I found the Log.e() and friends in the MainActivity class, but neither javadoc or code are attached so I'm pretty much guessing at the API. Specifically, the TAG.
This also hampers other grokking of the API, since I can't just hover or command-click on a method to see what it does. For example, I can't click through to see what methods there are on Manager or what overloads of getDatabase() may exist.
I didn't find it here either:
http://developer.couchbase.com/mobile/develop/references/couchbase-lite/couchbase-lite/index.html
I'm not sure how hard it is, but it'd be a useful enhancement to have the javadoc or sources attached. I know this follows the android.util.Log class, but since it's pointing to our own com.couchbase.lite.util, it's up to us to link the javadoc.
Perhaps this is actually a bug? I don't actually see a good reason for us to be using a Couchbase extended class for logging in a sample app over the canonical logging methods.
The text was updated successfully, but these errors were encountered: