Client-side example mistakenly refer to wrong name "symbol" in PrivateChannel doc

[YaoYao-dd]

Minor Issue

Client-side example mistakenly refer to wrong name "symbol" in PrivateChannel doc， it should be 'ticker' like below.

const resolution3 = await fdc3.raiseIntent("QuoteStream", { type: "fdc3.instrument", id : { **ticker**: "AAPL" } });
    try {

for below reasons:

1. make client-side and sever-side be consistent, both use 'ticker',
2. content data standard also defines instrument type with 'ticker'.

Area of Issue

[ ] App Directory
[*] API
[ ] Context Data
[ ] Intents
[ ] Desktop Agent Bridging
[ ] Use Cases
[ ] Other

[YaoYao-dd]

I can open PR to fix this if necessary, thanks.

[kriswest]

You are correct, there is an error here:

FDC3/docs/api/ref/PrivateChannel.md

Line 80 in aaa2a80

const resolution3 = await fdc3.raiseIntent("QuoteStream", { type: "fdc3.instrument", id : { symbol: "AAPL" } });

When raising a PR to fix this, it should also be fixed in past versions:

• FDC3/website/versioned_docs/version-2.1/api/ref/PrivateChannel.md

  Line 80 in aaa2a80

  const resolution3 = await fdc3.raiseIntent("QuoteStream", { type: "fdc3.instrument", id : { symbol: "AAPL" } });

• FDC3/website/versioned_docs/version-2.0/api/ref/PrivateChannel.md

  Line 75 in aaa2a80

  const resolution3 = await fdc3.raiseIntent("QuoteStream", { type: "fdc3.instrument", id : { symbol: "AAPL" } });

And a Changelog entry in the FIxed section would also be appreciated: https://github.com/finos/FDC3/blob/main/CHANGELOG.md

[bingenito]

I verified the pending .NET sample in #1108 has Ticker as the ID property

[YaoYao-dd]

will raise PR, thanks @kriswest

[YaoYao-dd]

PR opened, #1314, thanks

[kriswest]

closed as completed