# React: Known pain-points around signal initialization

**URL:** <https://discuss.ocaml.org/t/react-known-pain-points-around-signal-initialization/7934>\
**Category:** Learning\
**Tags:** react\
**Created:** [May 29, 2021, 7:51am UTC](https://discuss.ocaml.org/t/react-known-pain-points-around-signal-initialization/7934 "2021-05-29T07:51:12Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![orbitz](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/orbitz/32/110_2.png) [@orbitz](https://discuss.ocaml.org/u/orbitz)\
**Post date:** [May 29, 2021, 8:49am UTC](https://discuss.ocaml.org/t/react-known-pain-points-around-signal-initialization/7934/2 "2021-05-29T08:49:21Z")

</div>

I found [Your production web stack in 2020 - #10 by smondet](https://discuss.ocaml.org/t/your-production-web-stack-in-2020/6691/10) which references the `.value` traps.

In my case I tried changing it to `ReactiveData.from_signal (React.S.fmap f [] some_signal)` which at least avoid the exception, but the list doesn’t seem to change with my signal getting updated (at least in my test case).

---

_[View the full topic](https://discuss.ocaml.org/t/react-known-pain-points-around-signal-initialization/7934)._