-
Notifications
You must be signed in to change notification settings - Fork 6
Use unique channel names #16
Copy link
Copy link
Open
Labels
part:clientAffects the client codeAffects the client codepriority:lowThis should be addressed only if there is nothing else on the tableThis should be addressed only if there is nothing else on the tabletype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
Milestone
Metadata
Metadata
Assignees
Labels
part:clientAffects the client codeAffects the client codepriority:lowThis should be addressed only if there is nothing else on the tableThis should be addressed only if there is nothing else on the tabletype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
What's needed?
When the client create new channels, it uses a fixed string
f"raw-component-data-{component_id}", which means multiple instances of the client will use the same name for channels, which could be confusing/misleading when looking at the logs.Proposed solution
Add some
nameto the API client itself so it can be used in the logs too, defaulting to some short hash that will be unlikely match the auto-generated hash of other API client instances.