Skip to content

feat: reversed lack of support to support capabilities #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
grimly wants to merge 1 commit into from
Closed

feat: reversed lack of support to support capabilities #19

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions service/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -335,18 +335,21 @@ components:
$ref: '#/components/schemas/featureCacheInvalidation'
flagEvaluation:
$ref: '#/components/schemas/flagEvaluation'
required:
- name
flagEvaluation:
type: object
description: Configurations specific for flag evaluations in OFREP provider implementation
properties:
unsupportedTypes:
description: A list of unsupported types by the flag management system. Evaluating a flag of a listed type through OFREP provider will result in an error and yield the default value.
supportedTypes:
description: |
A list of supported types by the flag management system.
Evaluating a flag of an unlisted type through OFREP provider will result in an error and yield the default value.
type: array
items:
type: string
enum: [int, float, string, boolean, object]
examples:
- ["object", "int", "float"]
- [ boolean, integer, decimal, string, object ]
featureCacheInvalidation:
type: object
description: Configuration for the cache cacheInvalidation
Expand All @@ -365,5 +368,3 @@ components:
description: minimum polling interval (in millisecond) supported by the flag management system. The provider should ensure not to set any polling value under this minimum.
examples:
- 60000
required:
- name