Remove support for single type in queries #110
Conversation
|
Since this is a breaking change, it would be useful to add a note on the compatibility implications (ie legacy clients will be sending a single type ID) |
| @@ -218,6 +218,7 @@ <h4>This Draft</h4> | |||
| <p>Collection of changes which make the API conform to the REST principles.</p> | |||
| <ul> | |||
| <li>Remove support for flyouts;</li> | |||
| <li>Remove support for supplying a single type in a reconciliation query without enclosing it in an array;</li> | |||
There was a problem hiding this comment.
Yes, I have added a line about this here - would you want to see that elsewhere? Or written up differently?
There was a problem hiding this comment.
"Conform to REST principles" doesn't really draw the eye in the same was as "Incompatible changes" or some such, so I'd recommend a separate section. Ideally, it should be easy for a developer of a client or service to understand the implications of the change as described.
|
Won't versions of the spec help a little with determining breakage? I.E. if I don't change the version on my recon service that guarantees compatibility in that version and any clients using that same version? Let's continue in issue #78 |
|
Let's go the other direction as suggested by the discussion in #109. |
Closes #109