5758 - Navigation: Data errors

[yaguzmang]

Table validations

• Server-side table node validation

  • Validate table nodes per assessment/cycle/country and cache results in Redis
  • Revalidate edited nodes together with calculated dependents
  • Emit table validation updates to the frontend after node/dependency updates

• Frontend table validation flow

  • Fetch table validations when initializing table data
  • Remove client-side table validation
  • Remove frontend fetching of validation dependency table data
  • Show table validation errors in cells

• Validation summary and submission warning

  • Build validation summary for sections/subsections/tables
  • Show validation error indicators in the nav
  • Warn users before submitting to review

• Test table validations

  • Test cross-cycle validation when editing forest area
  • Test clearing validation errors after fixing data
  • Test updating dependent table validation errors after editing source data
  • Test showing validation errors on initial load
  • Test hiding validation UI on the print route
  • Test revalidating dependent max-area nodes after editing source data

Description validations

• Validate description text

  • Queue link validation after a user edits description text with links
  • Process edited description links in the verify-links worker
  • Store visited description links and locations in the links table
  • Update Redis description-link validations after single-description validation
  • Update Redis description-link validations after full-country/full-assessment link checks
  • Emit description text validation update events
  • Listen for description text validation events in the frontend
  • Rebuild the validation summary in the client when description text validations change
  • Include description text errors in validation summary
  • Show description text link validation errors in the description UI

• Validate data sources

  • Required fields

    • Validate data source fields that are required
    • Store fields validation results in Redis
    • Return/update required-field validation results in the frontend after save
    • Include data source errors in validation summary (backend and frontend)
    • Replace client side errors with server-side validation results
    • Show field validation errors in the nav indicators
    • Include field errors in the submit-to-review warning

  • Reference links

    • Queue reference-link validation after a user saves data sources with reference links
    • Validate reference links through the async links worker
    • Store visited reference links and locations in the links table
    • Clear stale reference-link locations/errors when a reference link is removed
    • Store reference-link validation results in Redis after link validation completes
    • Update Redis reference-link validations after single-description/data-source validation
    • Update Redis reference-link validations after full-country/full-assessment link checks
    • Emit reference-link validation update events
    • Fetch data source validations when initializing section descriptions
    • Listen for reference-link validation events in the frontend
    • Rebuild the validation summary when reference-link validations change
    • Show reference-link validation errors in the data sources UI

• Trigger links validation after approving/disapproving a link that is in a description

• In validateAll, validate also descriptions

• To see if we do:

  • Split validation reducer
  • In the links worker, use section name + description name instead of description ids

• Test description validations

  • Add tests for description text link validation flow
  • Add tests for data source validation flow

ODP validations