-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cellular: unified return value comments on API folder. #8814
Conversation
travis-ci/events failed, not related to this pr. |
I would assume yes, in features/cellular/framework/API/CellularInformation.h. How does this affect a user ? I restarted the events job |
It should not affect as implementation has not changed, it has never returned any size/length. Only way it affects is that application should expect nsapi_error_t instead of nsapi_size_or_error_t. Both are typedefs to signed int. I'll change to breaking change,. |
This is a breaking change because function prototype is modified. |
@AnttiKauppila we are committed to maintaining backward compatibility. Is this necessary? |
Even if those were different scalar types, I'd struggle to call this a "breaking change", but in this case they're both typedefs to the same thing! It's reformatting! |
I was wrong, I just quickly read the code. I checked and both return values are signed int's so it is not a breaking change after all! |
PR type updated accordingly. @bulislaw This should be ready for CI now, labeling as such |
CI started |
Test run: SUCCESSSummary: 4 of 4 test jobs passed |
Description
_ Fixed cellular API folder to follow same syntax when defining doxygen return values.
-CellularInformation had wrong return type (which is correct on deriving classes), fixed to correct return value. Does this make this Breaking change? Changed from nsapi_size_or_error_t to nsapi_error_t. Function implementation has returned only error codes.
@mirelachirica please review
Pull request type