Create a way to test the code
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- aws, javascript, shell
Research direction
The issue does not name any files, tests, or entry points. Start by inspecting the repository's Lambda entry point and current test or deployment configuration, then compare the proposed API Gateway mock and curl-based approaches. Done means a repeatable check confirms the redirect response and its status, effective URL, and redirect URL.
Written by the indexing model from the issue text.
Description
I can either:
- Create an API Gateway with integration type
mock - Create a shell script with a curl command like
curl -s -w "%{http_code}\n%{url_effective}\n%{redirect_url}\n" "API_GATEWAY_URL"and perhaps parse the output to determine if the response is as expected.
- Dominant language
- JavaScript
- Stars
- 22
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllTheMods/ATM-10-L#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SignalK/n2k-signalk#345 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
JuliaPluto/PlutoPlotly.jl#72 ·