Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: regression from #385 when callback is set to false #391

Merged
merged 2 commits into from
Jun 24, 2019

Conversation

studnitz
Copy link
Contributor

As I commented in PR #385, I actually introduced a regression when callback: false is set in redirect options,
as it tries to call normalizePath(callback), which calls callback.split(), which is not possible when it is set to false instead of a string.

This PR fixes this.

@codecov
Copy link

codecov bot commented Jun 23, 2019

Codecov Report

Merging #391 into dev will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@         Coverage Diff         @@
##            dev   #391   +/-   ##
===================================
  Coverage   100%   100%           
===================================
  Files         1      1           
  Lines         2      2           
===================================
  Hits          2      2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1833143...4b63f1b. Read the comment docs.

Copy link
Member

@pi0 pi0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@pi0 pi0 changed the title fix: fix regression from pr#385 when callback is set to false fix: regression from #385 when callback is set to false Jun 24, 2019
@pi0 pi0 merged commit 4605681 into nuxt-community:dev Jun 24, 2019
@pi0
Copy link
Member

pi0 commented Jun 24, 2019

Landed in 4.8.1

tanutsun pushed a commit to tanutsun/auth-module that referenced this pull request Dec 18, 2019
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.

None yet

2 participants