Under the hood
Render post-processing now handles 'Raster' components with dedicated logic instead of generic traversal
What
The internal tree-walking function used when applying render hooks to plugin UI now explicitly recognizes components of type 'Raster' and processes them with dedicated handling, rather than letting them fall through to the generic logic used for traversing child components. This change also factors out a shared set of helper functions used by both this walker and a related one.
Why
Giving 'Raster' components their own explicit handling suggests they need different treatment than ordinary child components during rendering, likely to ensure they're processed correctly rather than incorrectly treated as a generic container.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What visible difference this makes to how Raster components render isn't stated.