The new OpenAPI documentation that we are publishing with Unity gets confused by the many RefId types we have. The reason we have so many was an attempted to bring clarity about how that RefId is to be used (the RefId for the object itself, a direct reference, and indirect reference). However I believe these intents have been lost to time (I don't know which one to use when) and is now directly leading to confusing documentation rather than clarity they were create to bring.
I will start with a global review of this situation with the D3M team and report back!
The new OpenAPI documentation that we are publishing with Unity gets confused by the many RefId types we have. The reason we have so many was an attempted to bring clarity about how that RefId is to be used (the RefId for the object itself, a direct reference, and indirect reference). However I believe these intents have been lost to time (I don't know which one to use when) and is now directly leading to confusing documentation rather than clarity they were create to bring.
I will start with a global review of this situation with the D3M team and report back!