You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2018. It is now read-only.
In elm 0.17 the error is limited to ':', in elm 0.16 you also get many counts of the "Error: The notify function has been called synchronously! This can lead to frames being dropped." referenced in a number of issues including this one. This happens in reactor or via compiler.
What caught me (for longer than I'd like to admit) was using string: "localhost:123/foo/bar"--an easy mistake during development. Omitting the port, say "github.com/foo/bar", the request would have gone through as a relative URL (with a 404) and the bug/missing protocol would have been easy to spot.
I'm happy to open a PR, but I wanted to get some consensus on the right way to go about it. My suggestion would be to append "/" to the beginning any of the offending matches to avoid the error. Any concerns about potential side effects?
Elm has such great error reporting that it seems like this is worth fixing--it's a rare instance where something is going wrong and there's clear path on what to do.
The text was updated successfully, but these errors were encountered:
No Error in the following cases:
Error is thrown and no network call is made in the following cases:
In elm 0.17 the error is limited to ':', in elm 0.16 you also get many counts of the "Error: The notify function has been called synchronously! This can lead to frames being dropped." referenced in a number of issues including this one. This happens in reactor or via compiler.
What caught me (for longer than I'd like to admit) was using string: "localhost:123/foo/bar"--an easy mistake during development. Omitting the port, say "github.com/foo/bar", the request would have gone through as a relative URL (with a 404) and the bug/missing protocol would have been easy to spot.
I'm happy to open a PR, but I wanted to get some consensus on the right way to go about it. My suggestion would be to append "/" to the beginning any of the offending matches to avoid the error. Any concerns about potential side effects?
Elm has such great error reporting that it seems like this is worth fixing--it's a rare instance where something is going wrong and there's clear path on what to do.
The text was updated successfully, but these errors were encountered: