javascript-testing-patterns

Open Beginner friendly
#714 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
documentation

Research direction

Open plugins/javascript-typescript/skills/javascript-testing-patterns/SKILL.md and inspect the example around line 87. Confirm how the divide example is presented relative to pure functions, then update the example or its classification so the skill accurately distinguishes the behavior. Done means the testing-pattern guidance is idiomatic and consistent with the stated example.

Written by the indexing model from the issue text.

Description

enhancement
Preliminary Checks
  • I have read the Code of Conduct
  • I have searched existing issues to ensure this is not a duplicate
  • This is a constructive feature request for legitimate use cases
Scope

Existing plugin / agent / skill / command (improvement)

Target component (if scope is plugin/agent/skill/command)

javascript-testing-patterns

Problem description

the example https://github.com/wshobson/agents/blob/4236bb91f8395b0435f1d8b8baf9e8e4c69a8620/plugins/javascript-typescript/skills/javascript-testing-patterns/SKILL.md?plain=1#L87 is suppose to give examples to test pure functions however the divide function is not pure since its throwing an error

Proposed solution

the divide function example can be an example of impure functions

Use cases

not that important since most LLM's would understand this , but to make the skill a bit more idiomatic thats all

Alternatives considered

NA

Additional context

No response

Dominant language
Python
Stars
39.8k
Forks
4.2k
Avg merge
2d 2h
Merged PRs (30d)
20

Contributor guide

Open the contributing guide

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 wshobson/agents

All issues in wshobson/agents

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.