TemplateModelBase (MPS.Core (JetBrains MPS 2019.1.0))

java.lang.Object
- jetbrains.mps.generator.runtime.TemplateModelBase

All Implemented Interfaces:

TemplateModel

Direct Known Subclasses:

TemplateModelInterpreted
```
public abstract class TemplateModelBase
extends Object
implements TemplateModel
```
Base implementation of TemplateModel to use as superclass in generated code to facilitate future API changes

Constructor Summary

Constructors
Modifier Constructor Description

protected TemplateModelBase(TemplateModule module)

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method	Description
`TemplateModule`	`getModule()`
`GeneratorQueryProvider`	`getQueryProvider()`	FIXME PROVISIONAL CODE (return value), expose GQP in generator.runtime package Besides, now the caching is done in QueryProviderCache, so implementation is not obliged to keep the instance.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface jetbrains.mps.generator.runtime.TemplateModel
getConfigurations, getLongName, getSModelReference, getSwitches, loadTemplate

- Constructor Detail
  - TemplateModelBase
```
protected TemplateModelBase(TemplateModule module)
```
- Method Detail
  - getModule
```
public TemplateModule getModule()
```
    Specified by:
    
    getModule in interface TemplateModel
  - getQueryProvider
```
public GeneratorQueryProvider getQueryProvider()
```
    Description copied from interface: TemplateModel
    
    FIXME PROVISIONAL CODE (return value), expose GQP in generator.runtime package Besides, now the caching is done in QueryProviderCache, so implementation is not obliged to keep the instance. It could, however. XXX On one hand, we need a generic API to access queries and thus shall override the method in generated templates, OTOH, it's unlikely (error?) to use QueryProvider of a generated template as the code there invokes queries without the need for GQP (unless I decide to use QueryKey there and hold query instances). There might be another reason to give access to GQP from generated templates! If we enable a 'forced interpretation' mode when we interpret templates otherwise available as compiled. Not sure there's need for such functionality though, no requests have been made so far, nevertheless, I can't preclude a need like that one e.g. for bootstrap reasons.
    
    Specified by:
    
    getQueryProvider in interface TemplateModel
    
    Returns:
    
    null if there's no generated provider, or it had failed to load