Feature Request: Support additional WebDav-specified HTTP methods, such as LOCK
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 10k
- Forks
- 1.2k
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 92
Description
https://www.rfc-editor.org/rfc/rfc4918.html defines several HTTP methods to support WebDAV-like APIs, such as LOCK and UNLOCK. Unfortunately, these methods are not supported by Grape.
As these methods are not supported, ruby apps using Grape have to use other methods, such as POST and DELETE for locking and unlocking, such as in GitLab's support for Terraform remote state: https://gitlab.com/gitlab-org/gitlab/-/issues/207345.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with RFC 4918 and Grape's existing HTTP method dispatch or routing entry point; the issue does not name a file or test. Confirm how methods such as LOCK and UNLOCK should be accepted, then add coverage showing that WebDAV-specified methods are supported without requiring POST or DELETE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100