You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, if I use default config which has the template exclusion rules on <templateReader> node: <excludedBaseTemplate id="{8CA06D6A-B353-44E8-BC31-B528C7306971}" name="Rendering Parameters Template" />
I will have no possibility to know if the template is inherited from rendering parameters template or not.
What I would expect from this type of exclusion is that if we ignore that base template, it is obviously not included into de-serialized base templates property, as well as no fields from that base are template included into AllFields propery. However, I would still like to see base template ID in the template.TemplateInfo.BaseTemplateIds property.
That would mean that Leprechaun did read the .yaml properly, however did not de-serialize ignored base template.
Would that make sense?
The text was updated successfully, but these errors were encountered:
At the moment, if I use default config which has the template exclusion rules on
<templateReader>
node:<excludedBaseTemplate id="{8CA06D6A-B353-44E8-BC31-B528C7306971}" name="Rendering Parameters Template" />
I will have no possibility to know if the template is inherited from rendering parameters template or not.
What I would expect from this type of exclusion is that if we ignore that base template, it is obviously not included into de-serialized base templates property, as well as no fields from that base are template included into
AllFields
propery. However, I would still like to see base template ID in thetemplate.TemplateInfo.BaseTemplateIds
property.That would mean that Leprechaun did read the .yaml properly, however did not de-serialize ignored base template.
Would that make sense?
The text was updated successfully, but these errors were encountered: