Skip to content

OpenRegister refuses null for the required nullable LvsResult.dataExchangeJobId #1844

Open

Description

@rubenvdlinde

What is missing

OpenRegister refuses null for LvsResult.dataExchangeJobId, although the schema says null is allowed.

Why it matters

A result entered by hand has no exchange job. The property is required and nullable: true, and OpenRegister answers "should be type string but is null". So such a result cannot be saved.

Where

  • lib/Settings/learniq_register.json, schema LvsResult (lvs-result), property dataExchangeJobId, listed in required.

Already done

Done when

  • Saving an LvsResult with dataExchangeJobId: null works, through the API on a live instance.
  • Either learniq drops the field from required, or OpenRegister accepts null for a required nullable property. If the second, the fix goes to OpenRegister.

Activity

  1. github-actions commented on Oct 8, 2026

    @github-actions
    Contributor

    Thank you for opening this issue! It has been assigned to @rubenvdlinde for review.

    What happens next:

    1. A maintainer will review this issue and determine the appropriate action
    2. If accepted, it may be converted into an OpenSpec change for structured development
    3. You will be notified of any status changes

    Triage labels:

    • triage:accept-feature — accepted as a new feature
    • triage:accept-bugfix — accepted as a bug fix
    • triage:needs-info — more information needed
    • triage:wontfix — will not be addressed
    • triage:duplicate — duplicate of another issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingtriageAwaiting triage

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions