All I mean by 'deprecate' is to put that warning message in, and remove the endpoint from API v2. whether or not to rewrite it is a separate discussion.
On Thu, Sep 19, 2019 at 12:47 PM Jeremy Mitchell <[email protected]> wrote: > I am for this. To be clear, deprecate == > > - adding an alert to the response of POST /user/current/update along the > lines of "this endpoint is being deprecated, use PUT /user/current instead" > - not rewriting POST /user/current/update to Go > > Jeremy > > On Thu, Sep 19, 2019 at 10:55 AM ocket 8888 <[email protected]> wrote: > > > There's a handler in Perl for `POST /user/current/update` which does > > exactly what it looks like - updates the current user. > > This can already be done by just doing `PUT /user/current` or ever simply > > `PUT /users/{{ID}}`. > > So can we deprecate this endpoint? I'll add a deprecation notice if we > can > > get a consensus on that. > > >
