TIBCOSoftware/flogo

HTTP

Open

#360 建立於 2018年9月9日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)CSS (2,348 star) (290 fork)batch import
good first issuekind/enhancement

描述

Current behavior: Currently only supports GET, POST, PATCH, PUT, DELTE

Expected behavior: Should support all methods defined in the spec (https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html)

What is the motivation / use case for changing the behavior? Specifically, I'd like to implement the OPTIONS method as a means of providing OAS formatted descriptions on a per-endpoint basis.

Additional information you deem important (e.g. I need this tomorrow): I'd do this myself, but it's not clear to me where the source of the trigger exists.

貢獻者指南

技術棧
gorest api
領域
backendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
basic knowledge of HTTP methodsfamiliarity with Flogo source code
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Start by exploring the repository structure to locate where HTTP methods are currently handled (likely in a route or handler file). The reporter mentions uncertainty about the trigger location, so look for files related to HTTP handling or method dispatch. Once found, add support for the missing methods (e.g., OPTIONS) following the existing pattern. Check for any tests or documentation that need updating.