mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-03 00:52:32 +00:00
zeekayandHanzo Dev
5ac678fd84
PersonHog was the last of it, and it was not only a name. The package is personinsights and the types in it are already Person* -- the shipped descriptor under personinsights_client/proto/generated says PersonService and the tests say TestFakePersonClient -- but the .proto still declared PersonHogService. A client dialling one service name and a server built from a .proto declaring another is not a naming problem, it is a wire that does not connect; the only reason nobody hit it is that none of these services runs here yet. Five service declarations now say what the generated client has said all along. StreamHog was a second fictional company, invented so a Stripe mock had someone to bill. This fork already has Hedgebox, in five hundred fixtures, so the mock bills Hedgebox and there is one made-up company again instead of two. REVIEW_HOG was an enum member in three enums that had to agree, whose value has been `review` since the app was renamed. Only the member said otherwise. Every rule is in bin/debrand and every spelling is refused there, so a fresh upstream import lands on these names and none of them can come back. Two are named as outstanding rather than refused, with the reason each is still sayable: hogdesk survives inside applied migrations' choices lists, where Django compares it in Python and never writes it -- the member is Desk = "desk" and all three tables that store it hold no rows; sherlockhog keys a service in another repository that still calls itself that, and renaming our half would classify its traffic as a product that does not exist. Co-authored-by: Hanzo Dev <[email protected]>
20 lines
1.0 KiB
Protocol Buffer
20 lines
1.0 KiB
Protocol Buffer
syntax = "proto3";
|
|
package personinsights.leader.v1;
|
|
|
|
import "personinsights/types/v1/person.proto";
|
|
|
|
// PersonLeader is the internal write API exposed by leader pods.
|
|
// The router calls this service after hashing (team_id, person_id) to a
|
|
// partition and resolving the owning pod via the coordination routing table.
|
|
// The partition travels in the `x-partition` request-metadata header, set by
|
|
// the router, rather than in the request body — so the router can forward
|
|
// client request bytes verbatim without a decode/re-encode.
|
|
service PersonLeader {
|
|
// Apply property updates to a person. Merges $set, $set_once, and $unset
|
|
// diffs into the cached person state.
|
|
rpc UpdatePersonProperties(personinsights.types.v1.UpdatePersonPropertiesRequest) returns (personinsights.types.v1.UpdatePersonPropertiesResponse);
|
|
|
|
// Strong consistency read: returns the latest person state from the leader's cache.
|
|
rpc GetPerson(personinsights.types.v1.GetPersonRequest) returns (personinsights.types.v1.GetPersonResponse);
|
|
}
|