Tags: open-feature/spec
Tags
fix: Include hook hints in evaluation options type. (#250) <!-- Please use this template for your pull request. --> <!-- Please use the sections that you need and delete other sections --> ## This PR In section 4.5.1 of hooks it specifies: ``` > `Flag evaluation options` **MAY** contain `hook hints`, a map of data to be provided to hook invocations. ``` But it does not include this in the types.md file, which makes this a bit confusing. ### Related Issues <!-- add here the GitHub issue that this PR resolves if applicable --> ### Notes <!-- any additional notes for this PR --> ### Follow-up Tasks <!-- anything that is related to this PR but not done here should be noted under this section --> <!-- if there is a need for a new issue, please link it here --> ### How to test <!-- if applicable, add testing instructions under this section --> Signed-off-by: Ryan Lamb <[email protected]>
feat: add events (#182) Signed-off-by: Todd Baert <[email protected]> Co-authored-by: Justin Abrahms <[email protected]> Co-authored-by: Lukas Reining <[email protected]> Co-authored-by: Michael Beemer <[email protected]> Co-authored-by: Kavindu Dodanduwa <[email protected]> Co-authored-by: Thomas Poignant <[email protected]> Co-authored-by: Tom Carrio <[email protected]> Co-authored-by: Ryan Lamb <[email protected]> Co-authored-by: Ben Rometsch <[email protected]> Co-authored-by: Pete Hodgson <[email protected]>
chore: section clarity, harden API, providers (#149) **Marking Evaluation API and Providers `hardening`** and a few non-functional changes here that improve structure. specifically: - explicitly mark and number all sections - section headings have consistent numbering (provider section numbering was different than the other docs) - removed "draft" language An alternative to marking all of `provider` and `evaluation API` as hardening would be just marking all existing sections therein as hardening, which might be better since we'd have to do that anyway if we added a new experimental section. see: #146 for more on release goals. Signed-off-by: Todd Baert <[email protected]>
feat!: make error code an enum and include optional error message (#142) See #141 for context. Signed-off-by: Ryan Lamb <[email protected]> Co-authored-by: Todd Baert <[email protected]>
PreviousNext