Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

onAfterChange

Open
#849 11 comments 11 reactions 2 assignees View on GitHub

@MadCcc is already working on this.

Since Aug 24, 2023.

Assessment

This issue has not been assessed yet.

Description

The change in https://github.com/react-component/slider/pull/812 added /** @deprecated It's always better to use onChange instead */ to onAfterChange.

I use both onChange and onAfterChange.
We have questions which we finalise, but this should only happen when the user has released the slider on the value they are setting it to. Is there an alternative to onAfterChange that will allow me to keep this behaviour once it is removed?

Dominant language
TypeScript
Stars
3.1k
Forks
767
Avg merge
11m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 react-component/slider

All issues in react-component/slider

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.