---
title: "Comment by Pavel on \"Is it ok to pass setState as a prop in React?\" | Hashnode"
description: "Disagree, it is perfectly OK. First approach looks most clean and easy to understand. Context for this? Overengineering. Passing callbacks? What if you want to"
url: "https://hashnode.com/posts/is-it-ok-to-pass-setstate-as-a-prop-in-react/66783c0382eddce18ebd318c/comment/667bdf80bb6642d048a1b29b"
---

[Discussion](https://hashnode.com/posts/is-it-ok-to-pass-setstate-as-a-prop-in-react/66783c0382eddce18ebd318c)

Comment [Is it ok to pass setState as a prop in React?](https://hashnode.com/posts/is-it-ok-to-pass-setstate-as-a-prop-in-react/66783c0382eddce18ebd318c)

[Pavel](https://hashnode.com/@pavel827)

[Jun 26, 2024](https://hashnode.com/posts/is-it-ok-to-pass-setstate-as-a-prop-in-react/66783c0382eddce18ebd318c/comment/667bdf80bb6642d048a1b29b)

Disagree, it is perfectly OK. First approach looks most clean and easy to understand. Context for this? Overengineering. Passing callbacks? What if you want to increment by custom amount? You would have to pass callback with arguments and in that case it is better to pass just setter. Also setState has stable reference AFIAK, so no need to use useCallback later.