Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance validation process of the SQ #261

Open
thkoehler11 opened this issue Mar 5, 2024 · 1 comment
Open

Enhance validation process of the SQ #261

thkoehler11 opened this issue Mar 5, 2024 · 1 comment
Assignees

Comments

@thkoehler11
Copy link

thkoehler11 commented Mar 5, 2024

  • For the response call, it is imperative to include createdBy and change invalidTerms to invalidCriteria.

  • Currently, there is a gap in the system where validation for the 'structuredQuery' objects and their properties is missing. This includes validating each property within the 'structuredQuery' object against predefined criteria to guarantee that only valid and correctly formatted data is accepted

When multiple instances of the same criterion are present, distinguishing between them becomes problematic. To address this issue effectively, there is a proposal to introduce a unique identifier within the 'savedQueries' object schema. This identifier will enable clear differentiation between individual criteria instances, enhancing the clarity and usability of the system.

{
  "invalidCriteria": [
    {
      "hash": "contextTermcodeHash",
      "uniqueID": ???,
      "validationErrorCode": "???"
    }
  ]
}
@michael-82
Copy link
Collaborator

This issue requires further discussion in my/our opinion.

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

When branches are created from issues, their pull requests are automatically linked.

3 participants