Fix 'not-found' error key in test mode #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Olaleye-Blessing
force-pushed
the
not-found-key-error
branch
from
945c0a2 to
cb18431
Compare
Olaleye-Blessing
changed the title
not-found error key in test mode
Olaleye-Blessing
force-pushed
the
not-found-key-error
branch
from
cb18431 to
f6eca65
Compare
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
Olaleye-Blessing
force-pushed
the
not-found-key-error
branch
from
f6eca65 to
5d015ab
Compare
ikezue
approved these changes
Mar 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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