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

Proactive error messages in custom baseURL to prevent errors #36

Open
nixalon opened this issue Mar 11, 2024 · 0 comments
Open

Proactive error messages in custom baseURL to prevent errors #36

nixalon opened this issue Mar 11, 2024 · 0 comments

Comments

@nixalon
Copy link

nixalon commented Mar 11, 2024

(Don't know if this is a feature request or a bug)

When deploying using custom base URL, there is no error handling. The user can enter whatever string they want, but strange errors will occur if the string does not follow a certain pattern.

The pattern I realized works looks like this:

  • the string needs to start with https://
  • the string needs to end with /

If these steps aren't followed, the url can look like this:
image
In this case I had only written "/hem" as my custom base URL, which Noodl let me do. This caused the crazy url in the picture and that certain pictures did not build properly. It seemed as if a new /hem// was added every time i refreshed the page.

Noodl might be doing checks for .se or .com url's and that this bug only appeared because I'm using a .io url.

It would be helpful to have error messages in the custom base URL text field that make sure the two steps above are followed.

(I'm using URL path type Hash if that makes a difference)

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

No branches or pull requests

1 participant