Open oganm opened 2 months ago
I'll add a flag to trigger the old behavior. In general, when a ExperimentalFactor is rendered, I omit the EF inside its FVs because that is redundant.
Pushed a fix to the packages to work with this form but is there anything we can do so the specification matches what is actually going on?
Unless indicated by a required
property in the JSON schema, no fields are guaranteed to be present. I think I will consider adding a few required fields to the spec.
I can restore the fields, but mark them as deprecated in the context of an EFVO.
gemmapy and gemma.R currently work without those specific fields. but it's good to have the specification give a heads up when things vanish.
oh can you do context specific deprecations?
Hmm, not really because the models are shared. I can document individual fields though.
ah, just something akin to "pst i just removed this bit in this context" would be enough
According to the API specification, getDatasetDifferentialExpressionAnalyses endpoint is supposed to return
ExperimentalFactorValueObjects
as values ofexperimentalFactors
of the returnedresultSets
However an actual call to the endpoint would show that the output is missing
experimentalFactorId
andexperimentalFactorCategory
fields. I assume this was removed since these fields are redundant with the parent but not having such changes reflected in the specification causes invisible failures on occasion