JKHeadley/rest-hapi

Support OPTIONS and HEAD verbs

Open

#136 opened on Jul 3, 2018

View on GitHub
 (0 comments) (1 reaction) (0 assignees)JavaScript (1,181 stars) (156 forks)batch import
enhancementhelp wanted

Description

Is your feature request related to a problem? Please describe. For integration with upstream/downstream systems, a model's OPTIONS endpoint might need to be customized, say to allow a different CORS response.

HEAD would complete the support for all "read" verbs. It just needs to return what GET will return, minus the payload.

Contributor guide

Tech stack
javascriptnodejsrest 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.
half day
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.
mostly clear
Prerequisites
Node.jsHTTP methods
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the routing mechanism in rest hapi, likely in the source code for generating routes. Add handlers for OPTIONS and HEAD verbs similar to the existing GET handler but with appropriate responses (e.g., empty body for OPTIONS, same headers for HEAD). Check the hapi framework's documentation for default behavior. Implement and test with the existing test suite.
Support OPTIONS and HEAD verbs · JKHeadley/rest-hapi#136 | Good First Issue