esnet-security / SCRAM / 18979172634 / 1

93%

develop: 94%

Pull #163

github

test(restrict_changes): set this back to a 405 error

i think we do want to fail on the method, not on the user permissions. doing a 403 suggests that sometimes you can change an entry, but we always want to block PUT/PATCH as the client should just do a normal post every time and SCRAM handles the logic on our end. We don't want the client to have to track these things.

60 of 65 branches covered (92.31%)

Branch coverage included in aggregate %.

1208 of 1300 relevant lines covered (92.92%)

0.93 hits per line