coderef tag when scope=peer doesn't work

[amyhiggins]

coderef tag when scope=peer doesn't work

[robander]

In all dita-ot processing, scope="peer" is treated as a reference to a file that is not available to the toolkit for build purposes. For example, if you use scope="peer" on a topicref in a map, the referenced topics will no longer build (even if they really are present). Unless I'm missing something, I think this is consistent with all other processing for scope="peer".

[raducoravu]

As @robander said, if you want the code to actually appear you should not add scope=peer to it.
About this remark:

 but unfortunately it's seems to be required when building individual plugins with Oxygen XML WebHelp

Can you give us more details? Probably the cause is the link is outside of the main DITA Map folder.
If you are building the output from inside Oxygen, we have a transformation parameter named "fix.external.refs.com.oxygenxml" which might help if enabled:

https://www.oxygenxml.com/doc/versions/26.0/ug-editor/topics/dita-ot-external-refs.html

Recent versions of the DITA OT have a "preprocess2" processing option which no longer has problems with references outside of the published DITA Map folder but the default WebHelp output obtained with Oxygen is obtained with an older "preprocess" stage which has this problem.

[amyhiggins]

Ah okay, setting the scope="peer" issue aside, you seem to have pinpointed my problem ("...the default WebHelp output obtained with Oxygen is obtained with an older "preprocess" stage which has this problem"). Thanks for the help!

[raducoravu]

@amyhiggins if you are publishing using an Oxygen transformation scenario, if you open the DITA Map in the Oxygen DITA Maps Manager view and use the "Configure Transformation Scenarios" toolbar button, press "New->DITA OT transformation" and you will be able to choose "WebHelp Responsive using preprocess2 DITA-OT step" as a transformation type if you want to try how WebHelp Responsive with "preprocess2" would work. But we do not officially support it or run all our automatic tests with it.