Open lessthanjacob opened 4 months ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe
No
Describe the feature you'd like to see implemented
Currently, rendering logic is split between a
BaseHelpers
module (primarily), andBlueprinter::Base
(with the former also being included in the latter). I believe this was done to help "slim down"Blueprinter::Base
, butBaseHelpers
has seemingly turned into a sort of "junk drawer" of methods.Since rendering is a clearly defined concept in the context of
Blueprint
, it would be helpful to encapsulate relevant logic in a specific class (e.g.Renderer
), which would help with comprehensibility, testability, and extensibility moving forward.Describe alternatives you've considered
No response
Additional context
At the moment, the rendering flow looks something like so: