Closed ALoTron closed 3 years ago
As for the exception with missing https://
. This probably won't be fixed. The schema is an essential part of any URL, although web browsers try to hide it from the user for some reason. They probably do some black magic to figure out the correct schema and I'm not inclined to implementing this in BlockMap as well. Furthermore, this issue only arises when manually typing in the URL, which should be less necessary in the future.
As long as the user is not confronted with the exception anymore. This would seem like an internal bug instead of an user error.
True. I'll change the exception handling to make more clear that this error is a "you fucked up" and not a software bug or the like.
Environment info
2.1.0
openjdk 14.0.2
Arch Linux 5.4.52-1-lts
Description
Entering a server address as
example.address
instead ofhttps://example.address/
results in an IllegalArgumentException (first log below). Even a missing slash at the end (https://example.address
instead ofhttps://example.address/
) throws an exception (second log below). The second exception is not shown in the log ifblockmap-gui -v
was used.Steps to reproduce
blockmap-gui
example.url
orhttps://example.address
via File > Load from server or top address barActual result
The user is confronted with a stack trace.
Expected result:
Blockmap detects a address and completes it accordingly by adding a missing
https://
prefix, a missing slash at the end etc. If the error is intended behaviour the error dialog should display a user friendly error message instead of a stack trace at least.Debug log
Log for missing
https://
prefix. Actual server address has been replaced byserver.stuff
:Log for missing slash at the end. Actual server address has been replaced by
server.stuff
:Stack trace provided by the gui. Actual server address has been replaced by
server.stuff
: