-
Notifications
You must be signed in to change notification settings - Fork 298
feat(lazer): add allowed feeds per publisher, aggregated prices and feature flags to state #3019
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
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@Riateche |
// [required] If true, the publisher is active, i.e. it's allowed to publish updates. | ||
optional bool is_active = 4; | ||
// IDs of the feeds for which the publisher's price will be included in the aggregate. | ||
repeated uint32 allowed_feed_ids = 5; |
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 was wondering which one makes more sense, allowed_feed_ids per publishers or allowed_pub_ids per price feeds?
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.
It's a symmetric many-to-many relationship, so it's fine in either case. In the memory representation we can also reverse it if needed. Having a property on publisher makes governance actions look more natural.
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 like line 140 anticipated it being added in Feed, outdated now:
// TODO: list of permissioned publisher IDs.
…blisher-sdk version
Summary
Rationale
Implementing state and governance.
How has this been tested?