reazen / relude-url Goto Github PK

In relude-parse, @mlms13 added .rei files for the "extra" parser types that we have, so that we can have more safety and explicitness around how one can construct values of a certain type.

The .rei files make the types abstract, hide the data constructors, and only allow construction of values through parse functions, or through unsafeMake escape hatches, which throw exceptions for invalid input.

Right now, there is a lot of type/constructor heaviness in the APIs, so it would be nice to have a more friendly set of functions for safely constructing and manipulating URLs.

The goal would be to have a recommended way to "parse" a URL into our data structure using a string (and return an Option/Result), and a goal to safely construct a URL from it's parts in a nice clean way, which would ideally not require the use of Option/Result. However, since most parts of the URL are strings, it becomes hard to guarantee that the URL is valid and not use Option/Result (or throw exceptions).

We'll always have the parseExn style API for URLs, but if we can avoid that being the default use-case, it would be best.