TemplateRuleForConcept (MPS.Core (JetBrains MPS 2019.1.0))

All Superinterfaces:

TemplateRule

All Known Subinterfaces:

ReferenceReductionRule, TemplateDropAttributeRule, TemplateDropRootRule, TemplateReductionRule, TemplateRootMappingRule, TemplateWeavingRule

All Known Implementing Classes:

DropAttributeRuleBase, DropAttributeRuleInterpreted, DropRootRuleBase, MapRootRuleBase, ReductionRuleBase, ReferenceReductionRuleBase, RefReductionRuleInterpreted, TemplateDropRuleInterpreted, TemplateReductionPatternRuleInterpreted, TemplateReductionRuleInterpreted, TemplateRootMappingRuleInterpreted, TemplateWeavingRuleInterpreted, WeaveRuleBase
```
public interface TemplateRuleForConcept
extends TemplateRule
```
Captures aspect of template rules that depend on input node's concept.
In fact, might have been independent from rule (i.e. not part of a rule's API), MapConfig could have register rule against concept at startup/init, and then rules don't need to know (except for trace/debug/log purposes) concept they run against

Since:

3.3

- Method Summary
  
  All Methods Instance Methods Abstract Methods
  Modifier and Type Method Description
  
  boolean applyToInheritors()
  
  SAbstractConcept getApplicableConcept()
  - Methods inherited from interface jetbrains.mps.generator.runtime.TemplateRule
    getRuleNode

- Method Detail
  - getApplicableConcept
```
@NotNull
SAbstractConcept getApplicableConcept()
```
    Returns:
    
    concept to trigger this rule
  - applyToInheritors
```
boolean applyToInheritors()
```