Check for API Key before writing

Open
  • Is something wrong?
#25 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
api, authentication

Research direction

No file, test, or entry point is named. Start by locating the PUT, POST, and DELETE handlers and the API-key check, then compare their treatment with GET requests. Done means write requests require an API key while GET requests remain available, with coverage for each method.

Written by the indexing model from the issue text.

Description

feature

PUT, POST, DELETE

GETs are free.

Dominant language
JavaScript
Stars
11
Forks
5
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CenterForDigitalHumanities/rerum

All issues in CenterForDigitalHumanities/rerum

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.