The PrInfo struct is being populated directly from the JSON response without any error checking. If the response does not contain the expected fields, this could cause a panic. Consider adding error handling to ensure that the expected fields are present in the response.

[avikalpg]

          The `PrInfo` struct is being populated directly from the JSON response without any error checking. If the response does not contain the expected fields, this could cause a panic. Consider adding error handling to ensure that the expected fields are present in the response.

let pr_info = match (pr_data["destination"]["commit"]["hash"].as_str(), pr_data["source"]["commit"]["hash"].as_str(), pr_data["state"].as_str(), pr_data["source"]["branch"]["name"].as_str()) {
    (Some(base_head_commit), Some(pr_head_commit), Some(state), Some(pr_branch)) => PrInfo {
        base_head_commit: base_head_commit.to_string(),
        pr_head_commit: pr_head_commit.to_string(),
        state: state.to_string(),
        pr_branch: pr_branch.to_string(),
    },
    _ => {
        eprintln!("Failed to parse PR data: {:?}", pr_data);
        return None;
    }
};

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

[avikalpg]

@tapishr I think we should do this here. Muskan said that you had some reservations about using the match function - hence I am not doing this right away. But I understand the point that we just assuming that these fields will be present in the response from Bitbucket and will be correctly passed in the pubsub message.