Skip to content

Conversation

@krainboltgreene
Copy link

This resolves #12.

All session keys in a Plug.Conn get turned into strings, so there's no way to setup the maybe_subscribe for success in a test environment. This could be me just misunderstanding the situation.

@rvnash
Copy link

rvnash commented Mar 23, 2023

Any chance this getting merged? I have the same problem.

Olaleye-Blessing added a commit to Projectstake/phoenix_live_session that referenced this pull request Mar 29, 2023
issue:
All session keys in a Plug.Conn get turned into strings, so there's no way to setup
the maybe_subscribe for success in a test environment.

issue ref: pentacent#13
Olaleye-Blessing added a commit to Projectstake/phoenix_live_session that referenced this pull request Mar 29, 2023
issue:
All session keys in a Plug.Conn get turned into strings, so there's no way to setup
the maybe_subscribe for success in a test environment.

issue ref: pentacent#13
Olaleye-Blessing added a commit to Projectstake/phoenix_live_session that referenced this pull request Mar 29, 2023
issue:
All session keys in a Plug.Conn get turned into strings, so there's no way to setup
the maybe_subscribe for success in a test environment.

issue ref: pentacent#13
Olaleye-Blessing added a commit to Projectstake/phoenix_live_session that referenced this pull request Mar 29, 2023
Possible issue:
All session keys in a Plug.Conn get turned into strings, so there's
no way to setup the maybe_subscribe/2 for success in a test environment.

Issue ref:
pentacent#13
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.

Using Phoenix Live Session in tests causes a key not found error: __sid__

2 participants