Docstring update for interpretability

[dianaprior]

The docstring was wrong in describing the function output type.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[gemini-code-assist]

Code Review

This pull request updates the docstring for the get_shap_values function to accurately reflect that it returns a shap.Explanation object. However, the type hints for the return values of get_shap_values and get_shap, as well as the input type hint for plot_shap, remain set to np.ndarray. These should be updated to shap.Explanation to maintain consistency and ensure accurate static analysis.

[gemini-code-assist]

The docstring update correctly identifies the return type as shap.Explanation. However, several type hints in this file are now inconsistent with this change: the return type hint for get_shap_values (line 191), the return type hint for the inner get_shap (line 228), and the input type hint for plot_shap (line 115) all still specify np.ndarray. These should be updated to shap.Explanation (or Any) to ensure consistency across the module and avoid misleading static analysis tools. Note that since shap is imported locally, you may need to use string literals (e.g., "shap.Explanation") or TYPE_CHECKING to avoid runtime errors.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}