« Changelog History


Flagr v1.1.0 Release Notes

Release Date: 2019-03-20 // about 5 years ago

  • 🔄 Changes

    🍱 ❗️#239 introduced a semi-breaking change to the evalResult model. Since fields are no longer required, the zero value (e.g. null, 0) fields are ignored in the final evalResult payload. Old versions of goflagr, rbflagr, and jsflagr are compatible with this change.

    {
  "evalContext": {
    "enableDebug": true,
    "entityContext": {
      "hello": "world"
    },
    "entityID": "a1234",
    "entityType": "report",
    "flagID": 1,
    "flagKey": "kmmcd1nsd6ze56chh"
  },
  "evalDebugLog": {
    "segmentDebugLogs": [
      {
        "msg": "argument: state not found",
        "segmentID": 1
      }
    ]
  },
  "flagID": 1,
  "flagKey": "kmmcd1nsd6ze56chh",
  "flagSnapshotID": 8,
  "segmentID": 1,
  "timestamp": "2019-03-20T00:11:40Z",
  "variantAttachment": null,
  "variantID": null,
  "variantKey": null
}

    becomes

    {
  "evalContext": {
    "enableDebug": true,
    "entityContext": {
      "hello": "world"
    },
    "entityID": "a1234",
    "entityType": "report",
    "flagID": 1,
    "flagKey": "kmmcd1nsd6ze56chh"
  },
  "evalDebugLog": {
    "segmentDebugLogs": [
      {
        "msg": "argument: state not found",
        "segmentID": 1
      }
    ]
  },
  "flagID": 1,
  "flagKey": "kmmcd1nsd6ze56chh",
  "flagSnapshotID": 8,
  "segmentID": 1,
  "timestamp": "2019-03-20T00:11:40Z"
}