Re: building a mental model for the "current node" behavior
| Newsgroups | gmane.text.xml.xsl.general.mulberrytech |
|---|---|
| Message-ID | <[email protected]> |
You mean that one : https://our.umbraco.com/documentation/reference/templating/macros/xslt/xpath-axes-and-their-shortcuts ? Christophe Le 05/11/2020 à 17:50, Dave Pawson [email protected] a écrit : > On Thu, 5 Nov 2020 at 14:46, Martin Honnen [email protected] > <[email protected]> wrote: >> Am 05.11.2020 um 15:11 schrieb Chris Papademetrious >>> As a novice, I get confused remembering when the current node >>> does/doesn’t change. There’s also this, which I’m trying to grasp: >>> >>> https://www.w3.org/TR/xslt-30/#func-current >>> >>> What’s a good mental model for remembering this? >>> >>> 2. Inside an <xsl:template> block, is there a function that returns the >>> current **template-matched** node? >> That is what the >> current() >> function does, I am currently not sure why you first cite it and then >> seem to ask for another function doing the job of the current() function. > I think: > This relates to understanding the mental model? > > My view: > 'here' (.) is the current node / position in the input document tree > that is being processed. > > View the 'tree' in your head, and you may see the parents, siblings, > children of this node (point in the document tree). > Ken Holman has (had?) a good picture of this which may help. > Then decide what you want to do next? > When you have this model in your head comfortably, you may be happy using > xsl:apply-templates to process the children of the current-node, using > the xsl 'model'. > > > HTH > > > --~---------------------------------------------------------------- XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/3329386 or by email: [email protected] --~--