Emitters

YAML ==> Interface(List[Entities]) ==> Emitter() ==> CodeTarget

class yace.emitters.Emitter(searchpath: Path)

The default approach to transforming Entity in Model: to source-code-text is inheriting this class and utilizing the Jinja templates made available in self.templates. It might seem naive to utilize templating-engine like Jinja for a code-emitter, however, so far it seems to be the an incredibly simple approach.

This class populates self.templates with templates loaded for a given emitter-implementation. They work as Jinja usually does, a feature-addition allowing you to render a Jinja template within a Jinja template, via a custom-filter-function. For example, like so:

{{ entity | emit_entity }}

This works by seperating Jinja templates by filename-convention, template-names starting with “entity_{name}.template” are usable by this in-template renderer. Thus, for the example above, the template file is named entity_typedecl.

It assumes that ‘entity’ is an instance of Entity and uses a Jinja template to render it. This behavior is added as a means to keep all text-formating code inside the Jinja-templates, one does not need to goto the Python to see a different technique. Thus, all:

Entity ==> SourceCodeText

Is by default handled in one place: the Jinja templates.

render(template, args, filters)

Renders the given template, passing args…

yace.emitters.camelcase(symbol, pascalcase=True)

Format the given ‘symbol’ as (C|c)amelCase