最新3.0版本 双端都会出现的build问题

打开APP进入的是原生页面 点击按钮 跳转至flutterA页面 从flutterA页面 用BoostNavigator.of().push("b",arguments: {}, withContainer: true);的方式跳转到 flutterB页面 这个时候 A的build会执行 从B页面用BoostNavigator.of().push的方式再到C页面 A页面和B页面的build都会执行
demo上好像也是有这个问题的
请问这种机制就是这样设计的吗？
能有办法阻止A B 页面的build执行吗？

Reproduce the native-to-flutterA-to-flutterB-to-flutterC navigation flow described in the issue, including the BoostNavigator.of().push calls withContainer: true. Compare the behavior with the demo and inspect the navigation and build lifecycle around BoostNavigator. Done means determining whether the repeated A and B builds are expected and documenting or implementing a supported way to prevent them, if one exists.

Written by the indexing model from the issue text.