No it's not. It's what good OOD has _always_ looked like. Unfortunately, most people in the OOP world, like most people in the React world, didn't give a flip about good design, so they used Singleton to let their components reach out and grab what they wanted the way the React community uses Context.

The absolute best OOP paradigm I've ever seen was Robotlegs with Flash or Flex. Robotlegs was a dependency injection framework based on MVCS (Model, View, Controller, Service). The View was only responsible for showing the Model and communicating to the Controller what changes the user would like to make. The controller would send messages (in the Flash/Flex world, they were events, not actions) to the Service layer, which would decide whether and how to honor user requests for changes to the Model. It was the Service layer that would make api calls, if needed, and would change the Model and the send out an event that said how the model had changed. Then the Controllers attached to each View would provide the new model. This was 12-15 years ago.

If you hadn't heard, the React world doesn't care about the Reactive manifesto at this point, and Redux is so 2015 at this point. All the cool kids are boiling up pots of spaghetti to preserve their job security.