-
Notifications
You must be signed in to change notification settings - Fork 45
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.
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
feat: Update in-process resolver to support flag metadata #1102 #1122
feat: Update in-process resolver to support flag metadata #1102 #1122
Conversation
…e#1102 Signed-off-by: christian.lutnik <[email protected]>
...rc/main/java/dev/openfeature/contrib/providers/flagd/resolver/process/InProcessResolver.java
Outdated
Show resolved
Hide resolved
...est/java/dev/openfeature/contrib/providers/flagd/resolver/process/InProcessResolverTest.java
Outdated
Show resolved
Hide resolved
…-feature#1102 Signed-off-by: christian.lutnik <[email protected]>
1fa47fc
to
1285149
Compare
…e#1102 Signed-off-by: Todd Baert <[email protected]>
1285149
to
c08e7bc
Compare
@chrfwow this is definitely a step in the right direction - I think there's probably some null check missing related to the metadata causing the e2e failures: Working with @beeme1mr and a few others in in slack, we've decided another thing we'd want here is a very basic mechanism for reducing duplication: the ability to add metadata for the entire flag set at the "top level" which all flags inherit: {
"metadata": {
"foo": "bar"
},
"flags": {
"flag1": {
// ...
"metadata": {
// "foo": "bar" is automatically included, but can be overridden if defined in `flag1`
}
}
}
} The same thing is implemented here: open-feature/js-sdk-contrib#1120 cc @beeme1mr |
…to-support-flag-metadata' into feat/Update-in-process-resolver-to-support-flag-metadata # Conflicts: # providers/flagd/schemas
…-feature#1102 Signed-off-by: christian.lutnik <[email protected]>
…-feature#1102 Signed-off-by: christian.lutnik <[email protected]>
...test/java/dev/openfeature/contrib/providers/flagd/resolver/process/model/FlagParserTest.java
Outdated
Show resolved
Hide resolved
...rc/main/java/dev/openfeature/contrib/providers/flagd/resolver/process/InProcessResolver.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found one small issue here
…-feature#1102 Signed-off-by: christian.lutnik <[email protected]>
…to-support-flag-metadata' into feat/Update-in-process-resolver-to-support-flag-metadata # Conflicts: # providers/flagd/src/main/java/dev/openfeature/contrib/providers/flagd/resolver/process/InProcessResolver.java
…-feature#1102 Signed-off-by: christian.lutnik <[email protected]>
...ava/dev/openfeature/contrib/providers/flagd/resolver/process/storage/StorageQueryResult.java
Outdated
Show resolved
Hide resolved
...rc/main/java/dev/openfeature/contrib/providers/flagd/resolver/process/InProcessResolver.java
Show resolved
Hide resolved
…-feature#1102 Signed-off-by: christian.lutnik <[email protected]>
…-feature#1102 Signed-off-by: christian.lutnik <[email protected]>
Signed-off-by: Todd Baert <[email protected]>
Signed-off-by: Todd Baert <[email protected]>
This PR
Adds support for flag metadata in the in-process resolver
Related Issues
Fixes #1102