PayString/paystring

DELETE does not actually delete a user?

0xCLARITY opened this issue · 1 comments

0xCLARITY commented

Expected Behavior

When I DELETE a user using the Admin API, and then subsequently GET that user using the public API with a header of payid+json, I should get a 404 - Not Found.

Actual Behavior

I get a 200 - OK, with a payload including the payId and an empty addresses array.

Context

When I inspect my local database, this PayID does not actually exist anymore after the DELETE operation, so there is probably a bug in our Public API and how we handle the payid+json header.

Steps to Reproduce

  1. Spin up the PayID server
  2. DELETE 127.0.0.1:8081/users/alice$127.0.0.1
  3. GET http://127.0.0.1:8080/alice + Accept: application/payid+json
0xCLARITY commented

Closed by #598