fix cargo nightly fmt checks

Author: bug-ops

crates/rmcp/src/service/client.rs

@@ -21,7 +21,6 @@ use crate::{
     transport::DynamicTransportError,
 };
 
-
 /// It represents the error that may occur when serving the client.
 ///
 /// if you want to handle the error, you can use `serve_client_with_ct` or `serve_client` with `Result<RunningService<RoleClient, S>, ClientError>`
@@ -391,5 +390,4 @@ impl Peer<RoleClient> {
         }
         Ok(resource_templates)
     }
-
 }

crates/rmcp/src/service/server.rs

@@ -333,22 +333,22 @@ pub enum ElicitationError {
     /// The elicitation request failed at the service level
     #[error("Service error: {0}")]
     Service(#[from] ServiceError),
-    
+
     /// User declined to provide input or cancelled the request  
     #[error("User declined or cancelled the request")]
     UserDeclined,
-    
+
     /// The response data could not be parsed into the requested type
     #[error("Failed to parse response data: {error}\nReceived data: {data}")]
     ParseError {
         error: serde_json::Error,
         data: serde_json::Value,
     },
-    
+
     /// No response content was provided by the user
     #[error("No response content provided")]
     NoContent,
-    
+
     /// Client does not support elicitation capability
     #[error("Client does not support elicitation - capability not declared during initialization")]
     CapabilityNotSupported,