[Docs] COM-RPC tags

[TeknoVenus]

Move the tags documentation from ThunderTools repo into main documentation portal

Update to include latest tags

[github-actions]

PR Preview Action v1.1.1-25-g59e77e4
🛬 Preview removed because the pull request was closed.
2023-07-31 15:37 UTC

[TeknoVenus]

@sebaszm Made some minor tweaks to address comments.

If you could clarify the difference between the collapsed/extended compliant tags that would be appreciated.

[sebaszm]

@sebaszm Made some minor tweaks to address comments.

If you could clarify the difference between the collapsed/extended compliant tags that would be appreciated.

Thanks!

The snag is in the way how calls with a single parameter are defined. The JSON-RPC compliant way is to enclose them in an object, like params: { "name": "abcd" }. Historically there was also possible to collapse it, like params: "abcd", since there is only one parameter it doesn't need a name to be accessed. So the collapsed format means that methods, notifications and properties omit the enclosing object when there is only one parameter to pass. The exteneded format is a mixture where the collapse is only used for properties, since they enforce one parameter anyway, but not for methods and notifications. And compliant format is that all calls including properties use the enclosing object. Collapsed and extended are not recommended for new interfaces.