fix: improve error handling and logging in get_param_limits method #118
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several important changes to the
custom_components/econet300/api.py
file, focusing on improving error handling and logging for API parameter limits fetching. The most important changes are:Error Handling Improvements:
KeyError
,ValueError
,TypeError
,RuntimeError
) to theget_param_limits
method to catch and log specific errors that may occur during the fetching of parameter limits.Logging Enhancements:
get_param_limits
method to provide more detailed error messages, including the specific parameter name and the URI when limits data fetching fails.Code Structure:
try
block to theget_param_limits
method to ensure that errors are caught and handled appropriately, preventing the method from failing silently.These changes enhance the robustness and maintainability of the code by providing clearer error messages and handling potential exceptions more gracefully.