You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The BreakpointLocationsResponse containts a body that points to Vec<BreakpointLocation>. This is redundant and extends the encoding/decoding pattern, that shouldn't necessarily reflect the Rust API
Describe the solution you'd like
Transitively, it should just be a Vec<BreakpointLocation>. This is an example and is also applicable to the other responses that are enforcing an additional level via body when this, for the library level, is just redundant and doesn't improve the API
Describe alternatives you've considered
Using a literal representation of the specifications will not benefit from the features of Rust and might even be too confusing/verbose.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
vlopes11
changed the title
Simplify BreakpointLocationsResponse
Simplify ResponseOct 1, 2022
Is your feature request related to a problem? Please describe.
The
BreakpointLocationsResponse
containts abody
that points toVec<BreakpointLocation>
. This is redundant and extends the encoding/decoding pattern, that shouldn't necessarily reflect the Rust APIDescribe the solution you'd like
Transitively, it should just be a
Vec<BreakpointLocation>
. This is an example and is also applicable to the other responses that are enforcing an additional level viabody
when this, for the library level, is just redundant and doesn't improve the APIDescribe alternatives you've considered
Using a literal representation of the specifications will not benefit from the features of Rust and might even be too confusing/verbose.
Additional context
N/A
The text was updated successfully, but these errors were encountered: