CFML: tag <cfinclude template="…"> creates no edge; included functions are not attached to the component (mixins) #2651

Summary

Script-style include "x.cfm"; produces an imports edge. The tag form does not.

Our project has 246 <cfinclude template="…"> with a literal path, and none of them appears in the graph. All 9 imports edges in the index come from script includes.

Example

<!--- contens/core/baseform.cfc --->
<cfcomponent output="false">
	...
	<!--- shared parts of forms, lists and exports --->
	<cfinclude template="formlistshared.cfm">
</cfcomponent>

• formlistshared.cfm is indexed, and its functions (checkRightsPartPrepare, checkRightsPartRecords, …) appear as top-level function nodes.
• There is no edge from baseform.cfc to formlistshared.cfm.
• The functions are not members of baseform or its subclasses.

A component-level include is the common CFML mixin pattern: the included functions become methods of the including component and of every component that extends it.

Path styles seen (all literal)

Expected

1. An imports (or includes) edge for <cfinclude template="…">, the same as for the script form.
2. When the include sits at component level (outside <cffunction>), the included file's functions count as members of the component. Calls such as this.checkRightsPartPrepare() or unqualified calls in subclasses then resolve.