Welcome back.
We've added the current TimingsContract class and modified our database code to create the view.
The next step is to change the content provider to allow queries against the new view.
We've used constants for the uriMatcher.
So I'll start by creating a constant for the current timing.
Now that we've got a new value to match, we need to update the uriMmatcher function.
If the uri's for our new current timing view,
the matcher will return 300.
We should return the correct MIME type in the getType function.
I talked about MIME types back in section 12.
It's easy to forget to update them, because we're not using the MIME types. But they are a part of the
content provider API, so we should make sure that we return something valid.
All right.
The final change in here is to use the current timing view in the query function
okay.
That's all the background work completed. Our classes can now handle the new current timing view.
We just need to use it in the TaskTimerViewModel class.
I'll write
the code for that, and test it all, in the next video.
See you there.