Skip to content

Milestones

List view

  • Now that we have multiple components implementing flagd's JSON evaluator, we need a way to track and communicate the compliance of various implementations. Doing this by versioning the artifacts themselves isn't practical, since implementations will have their own fixes and breaking changes. _I propose rigorously version the flagd-schema, and then each implementation can note what version they support, and log warnings or throw (we should decide on these specifics)_. We already version the schema release iself, so some of this work is already done. Work required for this: - [ ] add a full version path to https://flagd.dev/schema/v0/flags.json (ie: https://flagd.dev/schema/v1.2.3/flags.json) - enhance the Makefile https://github.com/open-feature/flagd/blob/34756fe02d16e62e12b9baf65e983cd4157fa89e/Makefile#L128 to pull the latest version and create the corresponding folder to serve it from - [ ] add a version to the flagd-schema itself, in its `$id` property, currently it's `"$id": "https://flagd.dev/schema/v0/targeting.json"`, this should be made something like `"$id": "https://flagd.dev/schema/v1.2.3/targeting.json" - this should be automated with release please - [ ] update fladg specification to mention this versioning - update all the providers to leverage this and denote their support - [ ] Java - [ ] .NET - [ ] JS - [ ] Python

    No due date