Add parent_blueprint to PlanningInput
#9481
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are two main changes in this PR:
PlanningInputnow has aparent_blueprintfieldPlannerno longer takes a separate parent blueprint argument (since it comes with the planning input)There are a bunch of other mechanical changes, mostly related to trafficking in
Arc<Blueprint>s in various places.The rationale for change this is to ensure correctness as we get into #5552; I wrote this up in the new doc comment on
PlanningInputFromDb::assemble(); feedback welcome!This is staged on top of #9473. I had tried to make this change before doing that work, and updating the planner tests was a true nightmare. Happy to report updating the tests after that change was quite easy! (Didn't touch the planner tests at all, which only left a few that constructed
PlanningInputs outside the simulator.)