Update service blocks to use a node route context #236
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.
Fix #116
Changes the way services blocks get the current node, by changing from using the current route in the constructor and using a context mapping for the node route.
This allows the correct contents of the blocks to display in other modules such as layout builder.
To achive this, the provided blocks will need to be updated on existing sites with the update hook provided, this will add the required node context to the CTA, releated links and releated topics blocks.
The existing $this->node method is still present for backward compatability for other blocks that extend servicesBlockBase until they are updated to use the node route context value.