Re: [Mailman-Developers] Handling additions to REST API in client side

2017-12-29 Thread Barry Warsaw
On Dec 28, 2017, at 19:50, Abhilash Raj wrote: > PATCH won't fail when running partial updates, but it won't silently drop the > attributes that it doesn't support. So from client side, there is no real way > to > understand when to include that attribute which was added in a later version. Yes

Re: [Mailman-Developers] Handling additions to REST API in client side

2017-12-29 Thread Stephen J. Turnbull
Simon Hanna writes: > Up until now I was under the impression that the clients > (Postorius/Hyperkitty) always require the latest version of core. We don't require that the client be Postorius or Hyperkitty though. While in one sense we're not responsible for what third party clients do *at al

Re: [Mailman-Developers] Handling additions to REST API in client side

2017-12-29 Thread Simon Hanna
On 12/28/2017 06:19 PM, Mark Sapiro wrote: On 12/28/2017 08:33 AM, Simon Hanna wrote: * New keys (and values) can be added anytime This would make things like exposing new stuff easy. Clients that don't know about a field can just ignore it. But that doesn't address the original issue which