[jwrosewell]

Problem

The derived property page, added by #315 and merged into rc on 15 November, links the Rust example but not Go's, because Go's was still a draft when the page was written. 51degrees-go#137 merged it into Go's rc at 00:32 UTC on 15 November.

What the specification says

required-examples.md lines 30 to 52 at b3b2c0dd say every reference implementation MUST provide one example for the Derived Property Element, and that it MUST show a script held in the example and passed as text, a script read from a file beside the example, the same Pipeline built from a configuration file, and what the caller sees when a source Property is not available.

What changed

src/pipelineapi/features/derivedproperties.md, the Go tab. One sentence links the example, examples/pipeline/7_derived_property/main.go, and says what it shows, which is each of the four.

1. A script held as text, AddScript at line 225.
2. A script read from ReaderEngagement.yaml beside it, AddScriptFile at line 223.
3. The same Pipeline built from config.json, BuildFromConfiguration at line 187.
4. A request that leaves out session.PointerMoved, at line 140, whose derived properties then have no value and print the message naming it.

The page links blob/main, like its other links to the language repositories.

When this merges

After Go's Monday release reaches main, because the example is on Go's rc until then.

What remains

Node.js (51degrees-node#98) and Python (51degrees-python#125) have the element in open drafts, and Java has none yet. Each gets a tab on the page once its change is merged.

Build

Checks on the head, 425834d, all green.

• Preview built the documentation with Doxygen, with no warning from derivedproperties.md.
• utm-link-lint found no campaign tag, as this repository's .utm-lint.json ({ "mode": "forbid" }) requires.
• Only rc into main passed.