Zend\View\Renderer\JsonRenderer
JSON renderer
Synopsis
class JsonRenderer
implements
RendererInterface,TreeRendererInterface
{
- // members
- protected bool $mergeUnnamedChildren;
- protected ResolverInterface $resolver;
- protected string $jsonpCallback;
- // methods
- public mixed getEngine()
- public RendererInterface setResolver()
- public JsonRenderer setMergeUnnamedChildren()
- public JsonRenderer setJsonpCallback()
- public bool hasJsonpCallback()
- public bool mergeUnnamedChildren()
- public string render()
- public true canRenderTrees()
- protected array recurseModel()
- protected void injectChildren()
Hierarchy
Tasks
Line | Task |
---|---|
66+ | Determine use case for resolvers when rendering JSON |
127+ | Determine what use case exists for accepting both $nameOrModel and $values |
218 | please complete if append is true. must change old |
236+ | detect collisions and decide whether to append and/or aggregate? |
239 | detect collisions and decide whether to append and/or aggregate? |
Members
protected
- $jsonpCallback
—
string
JSONP callback (if set, wraps the return in a function call) - $mergeUnnamedChildren
—
Zend\View\Renderer\bool
Whether or not to merge child models with no capture-to value set - $resolver — Zend\View\Resolver\ResolverInterface
Methods
protected
- injectChildren() — Inject discovered child model values into parent model
- recurseModel() — Retrieve values from a model and recurse its children to build a data structure
public
- canRenderTrees() — Can this renderer render trees of view models?
- getEngine() — Return the template engine object, if any
- hasJsonpCallback() — Returns whether or not the jsonpCallback has been set
- mergeUnnamedChildren() — Should we merge unnamed children?
- render() — Renders values as JSON
- setJsonpCallback() — Set the JSONP callback function name
- setMergeUnnamedChildren() — Set flag indicating whether or not to merge unnamed children
- setResolver() — Set the resolver used to map a template name to a resource the renderer may consume.