This solves #13 in an attempt to justify the choice for vite! to be able to encode URL and text.
It wasn't clear this was intended and there was some oversight in user experience in the sense that /redirect would try to redirect to the text value instead of showing it. This merge request updated comments, the readme as well as the arguments for endpoint and their key value in response to better reflect this possible usage.
This solves #13 in an attempt to justify the choice for vite! to be able to encode URL and text. It wasn't clear this was intended and there was some oversight in user experience in the sense that
/redirectwould try to redirect to the text value instead of showing it. This merge request updated comments, the readme as well as the arguments for endpoint and their key value in response to better reflect this possible usage.