-
Notifications
You must be signed in to change notification settings - Fork 44
DS-2035 extended Subscription with filter object #1748
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: VladyslavHnes <[email protected]>
MateuszJaksa
left a comment
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.
Looks good on my side, thanks a lot for this extension.
| } | ||
|
|
||
| @JsonIgnoreProperties(ignoreUnknown = true) | ||
| public static class SubscriptionFilter { |
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.
Shouldn't we re-use the SpatialFilter here, and have a common "filter" object across all the places ?
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.
Ideally yes, that's what I tried to do initially. But the SpatialFilter object is part of xyz-util and if we try to import it we will get ourselves into a circular dependency situation. I tried moving it in this module too and it's a mess. So the best option is to simply have these values as separate fields
Signed-off-by: jaksa <[email protected]>
Signed-off-by: jaksa <[email protected]>
Signed-off-by: jaksa <[email protected]>
We need to extend Subscription class to contain an object that has jsonPaths and spatial filter data that Config API will populate.