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
not sure about the UX for that can be a filter show all , breaking change only
can be with tiny arrows to navigate to the next breaking change
the use case beeing public API , vs implementation where on public API there might have been lots of description update
it is interesting to focus on what actually is critical
Extension to this can be to have different level of "change" , breaking , compatibility (adding new fields , path), cosmetic (like description)
and clearly be able to differentiate those
The text was updated successfully, but these errors were encountered:
LasneF
changed the title
Capacity no navigate on the breaking change only
Capacity to navigate on the breaking change only
Jul 29, 2024
not sure about the UX for that can be a filter show all , breaking change only
can be with tiny arrows to navigate to the next breaking change
the use case beeing public API , vs implementation where on public API there might have been lots of description update
it is interesting to focus on what actually is critical
Extension to this can be to have different level of "change" , breaking , compatibility (adding new fields , path), cosmetic (like description)
and clearly be able to differentiate those
The text was updated successfully, but these errors were encountered: