Skip to content

Conversation

@darnjo
Copy link
Member

@darnjo darnjo commented Dec 1, 2025

This release fixes the following issues:

  • Critical package updates.
  • Updated Docker files and versions.
  • Not allowing multiple Fast Track suggestions for resources, fields, and enumerations.
  • Not allowing lookup value remapping using StandardLookupValue.

There are some remaining items:

  • Fix schema validation issues with En dash.
  • Add support for OAuth2 credentials for RESO Analytics 4.0.0 release.
  • Finish expansion enforcement using machine/human suggestions. Currently enforces exact matches but needs to support others.

darnjo and others added 30 commits May 6, 2025 09:26
Update referenced version to v2.0.0
@darnjo darnjo requested a review from mohit-s96 December 1, 2025 09:29
const { exit } = require('process');
const { DEFAULT_DD_VERSION } = require('../../../common');

const runRcfTests = async ({
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mohit-s96 - I think this needs to be filled in from that code you had been working on.

@@ -0,0 +1 @@
# TODO No newline at end of file
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mohit-s96 - we should add a README too similar to the DD 2.0 README. We need a new section on the root README about how to test RCF for certification, not just schema validation.

It should link off to its own page that explains how to use the tools and describes the files and outcomes. https://github.com/RESOStandards/reso-certification-utils/blob/main/lib/certification/data-dictionary/README.md

For DD 2.0 variations and schema validation testing, you could potentially just link to the sections from the current DD 2.0 testing guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants