Skip to content

Show clear compatibility message when gateway lacks main session key #459

@shanselman

Description

@shanselman

PR #457 now refuses to send chat messages until the gateway handshake resolves a canonical session key from sessionDefaults.mainSessionKey or the legacy mainKey. That is safer than falling back to a literal main, but older or incompatible gateways may leave the UI unable to send without a clear compatibility message.

Follow-up:

  • Confirm the minimum supported gateway always sends mainSessionKey or mainKey.
  • If not, surface a clear gateway update required / incompatible gateway message instead of only failing the send path.
  • Add a focused test for the incompatible-handshake path.

Context: identified during review of #457.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions