urilib by Oxyggen

Path and URI (URL) parsing library for Kotlin by Oxyggen.

Paths

The path parsing part is (probably) finished. To create a Path object call the Path.parse method:

val p = Path.parse("/first/second/third/../fourth/")

You can set an optional parameter pathSeparator. The default value is "/" (Linux, URL, etc...). Set value "\\" if you want to parse Windows style paths:

val w = Path.parse("C:\\temp\\abc.txt", pathSeparator = "\\")

Because it is designed to parse URL paths few simple few simple rules were introduced:

1. directory is the substring before last separator and file is the substring after last separator
2. path "" is the same as "/"
3. file name and extension separator is "."

I had to introduce rules 1) and 3) because these are not real or local paths, so it's not possible to check whether given path points to a file or a directory. Always add a separator at the end, if the path points to directory! So /dev/etc/ is directory but /dev/etc is file.

Examples

Parsing

val p = Path.parse("/first/second/third/../fourth/myfile.html")

property	value
p.complete	"/first/second/third/../fourth/myfile.html"
p.file	"myfile.html"
p.fileName	"myfile"
p.fileExtension	"html"
p.directory	"/first/second/third/../fourth/"

Normalization

Let's normalize this path and check the values:

val n = p.normalized

property	value
n.complete	"/first/second/fourth/myfile.html"
n.file	"myfile.html"
n.fileName	"myfile"
n.fileExtension	"html"
n.directory	"/first/second/fourth/"

Normalized path is a subclass of Path, so it's easy to check whether path object is normalized:

if (p is NormalizedPath) ...

This does not mean that Path object can't contain normalized path, but you can be sure that NormalizedPath object must contain normalized path.

Resolving relative paths

You can also resolve relative paths. Let's create relative r path and resolve it to absolute a using the original path p. Check also the normalized values from a (a.normalized):

val r = Path.parse("../anotherfile.html")
val a = p.resolve(r)

Result:

property	a.(property)	a.normalized.(property)
complete	"/first/second/third/../fourth/../anotherfile.php"	"/first/second/anotherfile.php"
file	"anotherfile.php"	"anotherfile.php"
fileName	"anotherfile"	"anotherfile"
fileExtension	"php"	"php"
directory	"/first/second/third/../fourth/../"	"/first/second/"

URI and URL...

Library was primarily created for c4k web crawling framework, but it's a standalone library... To parse URI and create URI object call method:

 val u = URI.parse("http://test.com")

This is the type hierarchy:

 URI
 ├── UnresolvedURI       (partial URI -> no scheme specified)
 └── ResolvedURI         (complete URI -> scheme & scheme specific part specified)
     ├── MailtoURI       (implemented, but not complete)
     └── ContextURI
         └── URL
             └── CommonURL
                 ├── HttpURL
                 └── FtpURL (not yet implemented)

As you can see the URI has 2 subclasses: UnresolvedURI and ResolvedURI. The UnresolvedURI is a relative URI, which is not complete. It can be resolved in a context, so each subclass of the class ContextURI implements a method parse. Using this method you can convert an UnresolvedURI to ResolvedURI (the runtime class will be for example HttpURL).

After parsing you can test the uri type:

 val u = URI.parse("http://test.com")
 if (u is HttpURL) {
    ...
 }

There are few methods to convert URI to string (depends on class hierarchy):

toString()              -> returns object info: Object@xxx (Uri)
toUriString()           -> returns the original URI (in case of relative URI: ./index.html)
toResolvedUriString()   -> returns resolved URI (./index.html in context test.com is test.com/index.html)
toNormalizedUriString() -> returns normalized, resolved URI string 

oxgl