在BLOC上有两个状态。
https：//bloclibrary.dev/#/blocnamingconventions：~：text =%E2%9C%85-，好，-sealed%20class%20CounterEvent
我认为你也应该更新Usebloc状态下的用户数据。我建议您使用SingleClass状态

看看这篇文章，希望对你有帮助：
The Observer Pattern: Facilitating Bloc Dependency Management in Dart

我不同意你的说法，文件不是很完整。您有一个简单的块到块通信问题，在www.example.com的体系结构部分中非常具体地解决了这个bloclibary.dev

来自文档：

第一个月

final OtherBloc otherBloc;
  late final StreamSubscription otherBlocSubscription;

  BadBloc(this.otherBloc) {
    // No matter how much you are tempted to do this, you should not do this!
    // Keep reading for better alternatives!
    otherBlocSubscription = otherBloc.stream.listen((state) {
      add(MyEvent());
    });
  }

  @override
  Future<void> close() {
    otherBlocSubscription.cancel();
    return super.close();
  }
}

字符串
While the code above is error free (and even cleans up after itself), it has a bigger problem: it creates a dependency between two blocs.个
Generally, sibling dependencies between two entities in the same architectural layer should be avoided at all costs, as it creates tight-coupling which is hard to maintain. Since blocs reside in the business logic architectural layer, no bloc should know about any other bloc.个
Application Architecture Layers个
A bloc should only receive information through events and from injected repositories (i.e., repositories given to the bloc in its constructor).个
If you're in a situation where a bloc needs to respond to another bloc, you have two other options. You can push the problem up a layer (into the presentation layer), or down a layer (into the domain layer).个
Connecting Blocs through Presentation You can use a BlocListener to listen to one bloc and add an event to another bloc whenever the first bloc changes.个

class MyWidget extends StatelessWidget {
  const MyWidget({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return BlocListener<FirstBloc, FirstState>(
      listener: (context, state) {
        // When the first bloc's state changes, this will be called.
        //
        // Now we can add an event to the second bloc without it having
        // to know about the first bloc.
        BlocProvider.of<SecondBloc>(context).add(SecondEvent());
      },
      child: TextButton(
        child: const Text('Hello'),
        onPressed: () {
          BlocProvider.of<FirstBloc>(context).add(FirstEvent());
        },
      ),
    );
  }
}

型
The code above prevents SecondBloc from needing to know about FirstBloc, encouraging loose-coupling. The flutter_weather application uses this technique to change the app's theme based on the weather information that is received.个
因此，在您的示例中，只需创建一个BlocListener<PostBloc>小部件，并在listener回调中，从AuthBloc触发一个事件，该事件通过该事件接收Posts的列表，并使用更新后的列表更新User对象。这样，在PostBloc的任何CRUD操作之后，User对象将自动更新。
我不推荐其他答案之一建议的观察者模式，因为a）它违背了库创建者推荐的模式，b）它比需要的更复杂。