Making React a Functional program by mapping behaviour to expected inputs and outputs.

[kinjal-basu]

To my fellow React developers,

I have been learning about Functional Programming recently. According to my knowledge so far, a purely functional program is one where every action / behavior is a map from an input type (parameters) to an output type (return) without mutating any state or accessing global objects or methods.

Since React promotes a functional approach to front-end development, I was curious about how much of React was functional itself. I know its impossible (read, idealistic) to create a purely functional program where user input is so prevalent but if we are able to at least list every possible behavior of React then it would be much simpler for developers using React to reason about their programs.

I find this endeavor to be worth my time but I am completely over my head regarding how to start listing every expected behavior of React. It would be very helpful if someone could point me in the right direction or tell me why this may be a doomed endeavor and save me a lot of time (although I would not be looking forward to this conclusion).

Thanking You
@kinjal-basu

[kinjal-basu]

Update:

I am starting by studying the React source code structure mentioned here - https://reactjs.org/docs/codebase-overview.html

Hoping that this will give some insight regarding code structure.

[kinjal-basu]

Would it be helpful if I use a note-taking app like obsidian or logseq to produce a graph structure of the entire react codebase where a note contains a function definition?

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!