url-parser | modify URLs while maintaining integrity | Parser library

The immediate problem is that int "page" will return a Maybe Int, but you're trying to use it with Result.withDefault, which, as the error message says, expects a Result. The fix for this is just to use Maybe.withDefault instead.

As you can see, request module is not part of dependencies as well devDependencies, please run

Evan has addressed this in the following GitHub Issue: https://github.com/elm/url/issues/6

tl;dr: It does nothing but is there for future use.

The Url parser just treats Url fragment as a String but you can replace # with ? before parsing:

This is by design. The proxy is only meant to aid in development so you can forward requests to a server elsewhere. This frees you from having to run an API server locally during front-end development. It mimics an environment where the Elm app and API server are served from the same host and port.

More info on the Webpack devServer can be found here.

When you build for production, the proxy concept is removed with the idea that you will be serving the Elm app and API back-end from the same host and port.

The fact that "Parser" appears as the type name and inside the type definition is particularly troubling.

Yes, on a first glance it's a bit confusing, but what's actually needed to be understood in this line:

The solution for the above error was correcting the way I was importing below components

Before

import { CDSEDetailsComponent, DirectDebitBankDetailsComponent, MachineDetailsComponent,} from "./reports";

After

import { CDSEDetailsComponent } from "./reports/cdse-details/cdse-details-component"; import { DirectDebitBankDetailsComponent } from "./reports/direct-debit-bank-details/direct-debit-bank-detai‌​ls-component"; import { MachineDetailsComponent } from "./reports/machine-details/machine-details-component";

Above changes needs to be made in app.module & app-routing.module

You can chain together for multiple query parameters. Let's say your SettingsRoute also expected a pageNumber integer argument:

I think you miss the authentication information and thus do not have the right to release to Sonatype OSS, as you try to deploy anonymously.