Closed dwalt closed 8 months ago
Was PR #261 sufficient to close this?
--Update: No, PR #261 does not solve these issues
@dwalt
The following will be fixed in PR #269
- Order of Report elements
- Evaluation Method is not an array
Actually, all of the issues in the original description will be resolved in the PR, not just these 2
@dwalt
Translator UI not working, network error
does not seem to be related to mdJson-schemas, should this be in here?
Scope is required
Does this apply to everywhere scope exists within data quality? (based on them all being single objects and not an array, they are all already limited to only one, but none of the schemas indicate the scope is required)
What I've done: (changes exist in PR #269 )
It mentions "Translator UI not working, network error" but I'm not sure what this refers to. If I were to guess, this is actually an issue in mdTools, not mdJson-schemas, because that translator UI is not working, but there's already an issue for that in the mdTools repository.
@jwaspin I would agree, I believe this was an artifact of previous Data Quality testing identifying that translation of DQ could not be tested.