Restrict methods

[Olegt0rr]

What do these changes do?

Are there changes in behavior for the user?

Related issue number

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b6883cb) to head (d88dd03).
Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #543   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines          475       487   +12     
  Branches        17        18    +1     
=========================================
+ Hits           475       487   +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Dreamsorcerer]

I think that's overkill, we only want to ensure that the user understands that GET is the only allowed method for browsers. A boolean should suffice.

[Olegt0rr]

Switched to bool

[Dreamsorcerer]

I've added changelog as we don't seem to have any docs. I think that's fine, so feel free to merge if you're happy with it.

[Olegt0rr]

@Dreamsorcerer, thanks

I got some thoughts :D

This way we helped to warn frontend developer with 405 status code after request.
But we still not warn backend developer. May be we need to also add a warning.warn?
Or fail not as answer to the front, but with RuntimeError?

[Dreamsorcerer]

But we still not warn backend developer. May be we need to also add a warning.warn?

I would expect a backend developer to test their code, even if only with Postman or similar, which is why this probably still works.
But, if you have a suggestion to create an error for the developer earlier, then that'd be even better.