The new nullable->nullable behavior isn’t covered by tests. Since TAPSchemaToVOSITest currently only validates schema, it wouldn’t catch regressions where nullable=true fails to emit the flag (or where nullable=false still emits it). Please add an assertion-based test that the generated VOSI output contains the nullable flag for at least one nullable column and omits it otherwise.
The new nullable->nullable behavior isn’t covered by tests. Since TAPSchemaToVOSITest currently only validates schema, it wouldn’t catch regressions where nullable=true fails to emit the flag (or where nullable=false still emits it). Please add an assertion-based test that the generated VOSI output contains the nullable flag for at least one nullable column and omits it otherwise.