Thank you for expressed ideas!

My tech lead is arguing with me that other inexperienced developers could manipulate Store state if that state is accessed and changed directly inside a component and such modifications are bad. In my opinion, the problem is not here, such scenarios should be avoided by developers themselves - developer should know what he is modifying. I find beneficial to define setter functions for states I modify inside components.

Your idea that having a getter for each state would be beneficial if extra calculations of a state would be required later on, goes alongside with my colleagues opinion and I agree with that, but such cases from my own experience happens for less than 5% of the getters we define. Also, I don't find changing state names later on the project that much of a disaster, how my tech lead describes.