Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-1494

Allow optional field in node-to-node and client-to-node

    Details

    • Type: Task
    • Status: Complete
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      As of now the validation schema for all messages is strict and doesn't allow new (optional) fields to be included at the end.

      As a long-term we should consider using protocolVersion, but for now it should be enough just to allow new (unknown) fields, so that old nodes don't break.

        Attachments

          Activity

            People

            • Assignee:
              ashcherbakov Alexander Shcherbakov
              Reporter:
              ashcherbakov Alexander Shcherbakov
              Watchers:
              Alexander Shcherbakov
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: