refactor(renderer): Separate render loop from single frame rendering #7
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.
This pull request refactors the CliRenderer to improve code clarity and
maintainability.
The core rendering logic has been extracted from the loop() method into a
new private method called _renderFrame().
This change allows renderOnce() to directly call the rendering logic without
invoking the entire loop, which is more efficient and semantically correct.
The loop() method now focuses on its primary responsibility: managing the
rendering loop and scheduling frames.
This refactoring improves the overall structure of the CliRenderer and makes
the code easier to understand and maintain. No functional changes are
introduced.