Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Dhruv Arora via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Dhruv Arora <a_dhruv@outlook.com>
Subject: Re: [PATCH 0/2] [GSoC] userdiff: adding typescript pattern
Date: Sat, 28 Mar 2026 17:42:26 -0700	[thread overview]
Message-ID: <xmqqtstzh3f1.fsf@gitster.g> (raw)
In-Reply-To: <pull.2251.git.git.1774734004.gitgitgadget@gmail.com> (Dhruv Arora via GitGitGadget's message of "Sat, 28 Mar 2026 21:40:02 +0000")

"Dhruv Arora via GitGitGadget" <gitgitgadget@gmail.com> writes:

> Description
> ===========
>
>  * Add builtin userdiff pattern for TypeScript files. Recognizes function
>    declarations, class definitions, arrow functions, and method definitions.
>    
>    * Handles common modifiers like export, async, static, etc
>
>  * Added tests for the typescript pattern in userdiff.
>
> Dhruv Arora (2):
>   userdiff: adding typescript pattern
>   fix(userdiff): sorted pattern and tests

We frown upon a patch series that makes mistakes in an earlier step,
only to fix them in a later step.  The "git rebase -i" command helps
us pretend to be more perfect developers than we actually are,
whipping your patch series into a shape that builds one small step
on top of another in a logical succession.  Such a patch series is
easier to understand than a history that faithfully records all the
stumbles the developer made until they reached the final solution.

Just have a single patch that adds the right pattern at the right
place and add necessary tests.

When/if your reviewers suggest further changes, the way you should
work on them is the same.  Pretend as if you discarded everything
you did, started from scratch, and reached the ideal result without
making any mistakes or taking any detours along the way.

Thanks.

>  t/t4018/typescript-class-method         |  7 +++++++
>  t/t4018/typescript-export-default-class |  7 +++++++
>  t/t4018/typescript-export-function      |  7 +++++++
>  userdiff.c                              | 15 +++++++++++++++
>  4 files changed, 36 insertions(+)
>  create mode 100644 t/t4018/typescript-class-method
>  create mode 100644 t/t4018/typescript-export-default-class
>  create mode 100644 t/t4018/typescript-export-function
>
>
> base-commit: ce74208c2fa13943fffa58f168ac27a76d0eb789
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2251%2FDhruv-0-Arora%2Fuserdiff%2Ftypescript-pattern-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2251/Dhruv-0-Arora/userdiff/typescript-pattern-v1
> Pull-Request: https://github.com/git/git/pull/2251

  parent reply	other threads:[~2026-03-29  0:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-28 21:40 [PATCH 0/2] [GSoC] userdiff: adding typescript pattern Dhruv Arora via GitGitGadget
2026-03-28 21:40 ` [PATCH 1/2] " Dhruv Arora via GitGitGadget
2026-03-28 21:40 ` [PATCH 2/2] fix(userdiff): sorted pattern and tests Dhruv Arora via GitGitGadget
2026-03-29  0:42 ` Junio C Hamano [this message]
2026-03-29  9:31 ` [PATCH 0/2] [GSoC] userdiff: adding typescript pattern Johannes Sixt
2026-03-29 14:39   ` Spelling JavaScript (was: Re: [PATCH 0/2] [GSoC] userdiff: adding typescript pattern) Ben Knoble

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqtstzh3f1.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=a_dhruv@outlook.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox