-
Notifications
You must be signed in to change notification settings - Fork 109
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
fix(1115): Identify subscribers by Identity AND Address #1121
Conversation
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, but a small comment would be 🍨 on the 🍰.
use spacetimedb_primitives::TableId; | ||
use std::ops::Deref; | ||
use std::sync::Arc; | ||
|
||
type Query = Arc<ExecutionUnit>; | ||
type Client = Arc<ClientConnectionSender>; | ||
type Id = (Identity, Address); |
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.
Given that we had a bug this was non-obvious, so could you add a comment explaining the why of this type?
Closes #1115. Previously subscribers were only identified by their Identity. However the same Identity can be associated to different Addresses.
56197f9
to
09d90b0
Compare
Closes #1115. Previously subscribers were only identified by their Identity. However the same Identity can be associated to different Addresses.
Closes #1115. Previously subscribers were only identified by their Identity. However the same Identity can be associated to different Addresses.
Closes #1115.
Previously subscribers were only identified by their Identity. However the same Identity can be associated to different Addresses.
Description of Changes
Please describe your change, mention any related tickets, and so on here.
API and ABI breaking changes
If this is an API or ABI breaking change, please apply the
corresponding GitHub label.
Expected complexity level and risk
How complicated do you think these changes are? Grade on a scale from 1 to 5,
where 1 is a trivial change, and 5 is a deep-reaching and complex change.
This complexity rating applies not only to the complexity apparent in the diff,
but also to its interactions with existing and future code.
If you answered more than a 2, explain what is complex about the PR,
and what other components it interacts with in potentially concerning ways.
Testing
Describe any testing you've done, and any testing you'd like your reviewers to do,
so that you're confident that all the changes work as expected!