TextGenContext (MPS.Core (JetBrains MPS 2019.1.0))

All Known Implementing Classes:

TextGenTransitionContext
```
public interface TextGenContext
```
FIXME WORK IN PROGRESS Everything TextGenDescriptor shall know about outer world. Client code shall make no assumptions about context being the same for any time period greater than single TextGenDescriptor.generateText(TextGenContext) call. Nested descriptors may receive brand new context instance. TODO likely shall expose TextUnit? Or it's part of TextBuffer? Technically, I'd like to keep TextBuffer independent from TextUnit. OTOH, why can't I use TextGenContext without TextUnit? It's in use with TextGenDescriptor#generateText(), which is proper place to invoke getTextUnit, but still, not 100% sure.

Since:

3.3

Method Summary

All Methods Instance Methods Abstract Methods
Modifier and Type	Method	Description
`TextBuffer`	`getBuffer()`
`SNode`	`getPrimaryInput()`	With transition to TextGen capable of generating text from a set of nodes instead of a single one (see `TextGenModelOutline.registerTextUnit(String, SNode...)`), we still need to know the node actual TextGen code runs for.

- Method Detail
  - getBuffer
```
@NotNull
TextBuffer getBuffer()
```
    Returns:
    
    text buffer associated with a unit being generated.
  - getPrimaryInput
```
SNode getPrimaryInput()
```
    With transition to TextGen capable of generating text from a set of nodes instead of a single one (see TextGenModelOutline.registerTextUnit(String, SNode...)), we still need to know the node actual TextGen code runs for.
    
    Returns:
    
    node active node being processed