feature: add GET /echo that returns the query message
Assessment
This issue has not been assessed yet.
Description
Problem
We need a trivial request→response round-trip to prove the coding agent can add a parameterized route and a test.
Outcome
GET /echo?message=hello returns HTTP 200 with JSON {"message":"hello"}. Missing message returns 400.
Spec reference
spec/features/example-happy-path.feature
Acceptance criteria
Given the Node service in src/
When a client calls GET /echo?message=hello
Then the response status is 200
And the body is JSON with message equal to hello
Given the Node service in src/
When a client calls GET /echo with no message query param
Then the response status is 400
And the body is JSON with an error field
Constraints
- Keep the change small under
src/ - Open a draft pull request; do not merge
- Update
docs/pr-evidence.md - Follow AGENTS.md
- Dominant language
- Gherkin
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from bcgov/tier2-pattern-test
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/tier2-pattern-test#22 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bcgov/tier2-pattern-test#21 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
bcgov/tier2-pattern-test#20 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bcgov/tier2-pattern-test#19 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bcgov/tier2-pattern-test#18 ·