Compare with diff-match-patch

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

Maintainers usually reply within 1 day

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
javascript
Domain
tooling

Research direction

Start by comparing jsdiff's current implementation with diff_match_patch_uncompressed.js and Neil Fraser's diff overview. Review the README and issue 225 for the proposed comparison, then determine whether the intended outcome is optimization work, README documentation, or both. Done would require an agreed scope and corresponding documented comparison or performance changes.

Written by the indexing model from the issue text.

Description

documentation performance

Key places to look seem to be:

Dominant language
JavaScript
Stars
9.2k
Forks
555
Avg merge
1d 9h
Merged PRs (30d)
5

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 kpdecker/jsdiff

All issues in kpdecker/jsdiff

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.