This works fine as long as the everything is in the same repo, but ideally you would want to have a separate repo for the documentation. There will be other documentation besides the class files and we want to keep them on a distinct cadence from code updates. 

When I try to use the INPUT reference to another repo, it fails with source is not a readable file or directory... skipping. I've read through the documentation and I can't find anything related to referencing a remote repo.

I'll post to their listserv and see if this is possible.

This looked interesting so I tried it on one of my repo's and it seems to create the documentation,  but when I open the index.html page I don't see the navigation display for the classes; it just displays the header page. I did notice at the end the following:

Running plantuml with JAVA...
type lookup cache used 0/65536 hits=0 misses=0
symbol lookup cache used 0/65536 hits=0 misses=0

Perhaps this is an issue?

Yes we have faced this issue with CacheStream global growing out of control. We have had to create custom purge utilities to clean this data up as well as making sure any of our persistent classes that leverage a Stream class will trigger deletes on the stream when our record is deleted.

You would think the product would be able to handle this as part of cleanup of Ens.messageHeader, but alas that is not the case.

Well you can have more than one cursor. The main problem is in the second query, we joined Ens.Messageheader to EnsLib_HL7.Message and referencing the Identifier field of EnsLib_HL7.Message was causing a compiler error on the SQL query. Once that field was removed, everything is fine. The oddity is the query would work fine on the Management Portal SQL web page, but would not work in code.

The error was  multiple Referenced macro not defined errors.

Adapting the sample code to connect to my own local IRIS, how do I define the location for intersystems-iris-native. I see this line of code const irisnative = require('intersystems-iris-native'). Do I need to make a copy of one of the iris.node files from the bin directory and add it it node-modules?

Also I am using node v13.8.0 - will iris1000.node work is do I need one specific to that version?