However, I’d still argue that it would be nice if a Coda table could be configured to not exhibit this behavior. From a typing perspective, it affects “downstream” functionality that has been built into the doc when Coda changes the types in a way that is incompatible with the expected type downstream.
There is another issue that I posted related to CrossDoc behavior that seems to be related to the same core problem.