Skip to content
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

draft(subscriptions): Introduce RPCSubscriptionData class #6434

Draft
wants to merge 9 commits into
base: shruthi/ref/introduce-abstract-subscription-data-class
Choose a base branch
from

Conversation

shruthilayaj
Copy link
Member

Draft, I want to make sure this is will do what I want it to do

@shruthilayaj shruthilayaj changed the title feat(subscriptions): Introduce RPCSubscriptionData class draft(subscriptions): Introduce RPCSubscriptionData class Oct 17, 2024
… into shruthi/feat/introduce-rpc-subscription-class
Comment on lines +123 to +130
@dataclass(frozen=True, kw_only=True)
class RPCSubscriptionData(SubscriptionData):
"""
Represents the state of an RPC subscription.
"""

table_request: str

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. the table_request is bytes, not a string
  2. we should be storing the name of the endpoint and the version of it. The API will evolve and we need to be able to change the model along with it


table_request: str

def build_request(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

returning a snuba Request object here does not make sense. The RPC implementations will build whatever requests are necessary and execute them

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants