Repository navigation
docs: Fix the crystal ball image path in the post processing docs - #4236
Merged
spydon merged 2 commits intoNov 18, 2026
Merged
Conversation
spydon
approved these changes
Nov 18, 2026
spydon
enabled auto-merge (squash)
November 18, 2026 08:12
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The Crystal Ball example image on the post processing page does not render.
doc/flame/rendering/post_processing.mdreferences../images/crystal_ball.png, which resolves todoc/flame/images/crystal_ball.png(does not exist); the image lives atdoc/images/crystal_ball.png. On the published page the<img>points toflame/images/crystal_ball.pngand returns 404.The path is now
../../images/crystal_ball.png, the same form the other pages underdoc/flame/components/use fordoc/images.Checklist
docsand added dartdoc comments with///.examplesordocs.Breaking Change?
Related Issues
None.