You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The behavior of OCDS Merge is to set the tag to compiled for compiledRelease, and to move the tag onto the versioned object for versionedRelease. In other words, the original tag field is omitted.
Assigning to @kindly to confirm. The docs don't describe the first behavior, which we can fix as part of this issue.
The text was updated successfully, but these errors were encountered:
@jpmckinney yes this is what I thought was expected behaviour. Was not aware that was not in the docs.
We need to put something in tag at the compiledRelease level as it is a required field.
This relates to #330 (about making a compiledRelease schema) as we could validate this there.
- Use omitWhenMerged to determine which fields to remove from versioned release schema
- Only include unversioned definitions if needed in versioned release schema
The behavior of OCDS Merge is to set the tag to
compiled
for compiledRelease, and to move the tag onto the versioned object for versionedRelease. In other words, the original tag field is omitted.Assigning to @kindly to confirm. The docs don't describe the first behavior, which we can fix as part of this issue.
The text was updated successfully, but these errors were encountered: