TIBCOSoftware/flogo

HTTP

Open

#360 opened on Sep 9, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)CSS (2,348 stars) (290 forks)batch import
good first issuekind/enhancement

Description

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.

Contributor guide

Tech stack
gorest api
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
basic knowledge of HTTP methodsfamiliarity with Flogo source code
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.