More derive(Debug)

src/calendar/remote_calendar.rs

@@ -32,6 +32,7 @@ static TASKS_BODY: &str = r#"
 
 
 /// A CalDAV calendar created by a [`Client`](crate::client::Client).
+#[derive(Debug)]
 pub struct RemoteCalendar {
     name: String,
     resource: Resource,

src/client.rs

@@ -97,6 +97,7 @@ pub(crate) async fn sub_request_and_extract_elems(resource: &Resource, method: &
 
 
 /// A CalDAV data source that fetches its data from a CalDAV server
+#[derive(Debug)]
 pub struct Client {
     resource: Resource,
 
@@ -106,7 +107,7 @@ pub struct Client {
 }
 
 
-#[derive(Default)]
+#[derive(Debug, Default)]
 struct CachedReplies {
     principal: Option<Resource>,
     calendar_home_set: Option<Resource>,

src/provider.rs

@@ -45,6 +45,7 @@ impl SyncResult {
 ///
 /// Usually, you will only need to use a provider between a server and a local cache, that is to say a [`CalDavProvider`](crate::CalDavProvider), i.e. a `Provider<Cache, CachedCalendar, Client, RemoteCalendar>`. \
 /// However, providers can be used for integration tests, where the remote source is mocked by a `Cache`.
+#[derive(Debug)]
 pub struct Provider<L, T, R, U>
 where
     L: CalDavSource<T>,

src/resource.rs

@@ -1,7 +1,7 @@
 use url::Url;
 
 /// Just a wrapper around a URL and credentials
-#[derive(Clone)]
+#[derive(Clone, Debug)]
 pub struct Resource {
     url: Url,
     username: String,