Open dboltovskyi opened 6 years ago
@robinmk, please advise on the issue which API is correct
HMI API (are optional) | MOBILE API (are mandatory) |
---|---|
GPSData | GPSData |
TireStatus | TireStatus |
BeltStatus | BeltStatus |
DeviceStatus | DeviceStatus |
@robinmk, any updates on this question?
I think they should be marked optional to not cause any compatibility issues. @JackLivio @mrapitis @yang1070 , thoughts?
These structs should probably have been originally made optional in the mobile api to allow the hmi to send data when its available. Moving forward I think we may need to deprecate the mandatory flags and resolve inconsistencies.
@robinmk, @mrapitis so is it final decision to mark mentioned above parameters as an optional?
We will bring this up as an item for discussion in the next SDLC meeting so that the entire SDLC is aware of the problem. Based on the feedback there we will plan our next steps.
@robinmk, any updates regarding this issue?
@robinmk Do we have any updates?
@robinmk Please reply : do we have any updates related to this issue?
No, there is no new updates on this. I will have to follow up on this.
the proposal aligning TireStatus API https://github.com/smartdevicelink/sdl_evolution/blob/da73ad1c298fd5cc3517c9e0a4a368974c0a4a57/proposals/0236-TireStatus-Mismatch.md
There is a discrepancy in HMI and MOBILE APIs for some vehicle data structures on optionality of parameters: E.g.: In GetVehicleData response there is a parameter "gps" with type "GPSData" In HMI API all parameters of GPSData structure are optional, but in MOBILE API all of them are mandatory. Currently SDL is unable to transfer response from HMI to Mobile application with some missing parameters of GPSData structure.
List of structures with differences:
Please clarify which API is correct?