Handle None for environments that have data directories

[ryardley]

          _:warning: Potential issue_

Handle potential None values when retrieving configuration directories

The code uses unwrap() on dirs::config_dir() and dirs::data_local_dir(), which will cause the program to panic if these functions return None. This can happen in environments where the configuration or data directories are not set. Consider handling the None case to provide a more robust implementation.

Apply this diff to handle potential None values:

-    pub fn config_dir() -> PathBuf {
-        dirs::config_dir().unwrap().join("enclave")
+    pub fn config_dir() -> Option<PathBuf> {
+        dirs::config_dir().map(|dir| dir.join("enclave"))
     }

-    pub fn data_dir() -> PathBuf {
-        dirs::data_local_dir().unwrap().join("enclave")
+    pub fn data_dir() -> Option<PathBuf> {
+        dirs::data_local_dir().map(|dir| dir.join("enclave"))
     }

You'll need to handle the change in return types from PathBuf to Option<PathBuf> throughout your codebase to ensure proper error handling if the directories are unavailable.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

    pub fn config_dir() -> Option<PathBuf> {
        dirs::config_dir().map(|dir| dir.join("enclave"))
    }

    pub fn data_dir() -> Option<PathBuf> {
        dirs::data_local_dir().map(|dir| dir.join("enclave"))
    }

Originally posted by @coderabbitai[bot] in #156 (comment)