Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Switch to POST?

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
r
Domain
api

Research direction

The issue names no files, tests, or entry points. First read the request-handling documentation or entry point and clarify whether the project should use GET or POST, including the expected treatment of sensitive parameters; done means the decision and its implementation scope are documented.

Written by the indexing model from the issue text.

Description

When I designed this, I made a conscious decision to use GET requests rather than POST requests. I'm not convinced this was the correct approach and I need to further think through the pros and cons. It probably makes little difference in the implementation but would ensure that sensitive data can be transmitted this way. I'm having trouble picturing when a system like this would pass sensitive data as a parameter, but I supposed it could happen.

Dominant language
R
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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 dmarx/dispatchr

All issues in dmarx/dispatchr

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.