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(could not connect to server): explain the reasons #216

Merged
merged 1 commit into from
Jan 22, 2020

Conversation

SanderElias
Copy link
Contributor

This pr adds better handling when we fail to traverse routes in the angular app, and explains the
most common reasons.

closes #40

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Other... Please describe:

What is the current behavior?

Scully throws a non-descript error (could not connect to server) when it can not properly parse the routes n the application

Issue Number: #40

What is the new behavior?

It describes what happened and gives you a path to a solution to the issue.
Also, it warns when there is no (empty) home route.

Does this PR introduce a breaking change?

  • Yes
  • No

…t connect

This pr adds a better handling when we fail to traverse routes in the angular app, and explains the
most common reasons.

closes #40
@SanderElias SanderElias merged commit fc4f5c1 into master Jan 22, 2020
@SanderElias SanderElias deleted the sander/couldNotConnect branch January 22, 2020 11:26
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.

Could not connect to server
2 participants