Implemented normalizeHttpPath option

[fabien]

See previous discussion: loopbackio/loopback-datasource-juggler#199

[slnode]

Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test."

[fabien]

See: strongloop/loopback#433 for LB integration

[raymondfeng]

@ritch Can you help @fabien here?

[fabien]

@ritch @raymondfeng this is currently a blocking issue for me - AFAIK there's no good way to change the remoting path of the base models, and frankly having non-normalized paths in urls is just unacceptable to me; it should never have slipped into LB 2.0 in the first place IMHO: /Users ???

[ritch]

I think we need to support url formats instead of a flag to normalize URLs this way. This is what I am thinking...

function RemoteObjects() {
  // ...
  this.addFormat({
    for: 'url',
    name: 'dashed'
  }, function(original) {
    return dasherize(lowercase(original));
  });
  // ...
}

// usage (eg in a loopback app)
app.remotes().format('url', 'dashed');

// custom style
app.remotes().addFormat('url', 'my style', myFormatFn);

// we can also make other things format-able in the same way (note: different arg style)
app.remotes().addFormat('response body', 'namespaced', function(body) {
  return {
    myNamespace: body
  };
});

[fabien]

@ritch +1 although I would be just as happy with:

// usage (eg in a loopback app)
app.remotes({ formatting: { url: 'dashed' } });

[bajtos]

Since none of us have time to implement the version with all bells and whistles, I am proposing to go with the solution proposed by @fabien.

It is flexible enough in the sense that it can be easily extended to support a function value of normalizePath and thus allowing the user to apply whatever custom normalization he wants.

// use the default implementation as provided by this pull request.
normalizePath: true` 

// the same configuration expressed as a custom function
// can be implemented later
normalizePath: function(fragment) { 
  return inflection.transform(fragment, ['underscore', 'dasherize']); 
}

Another pro of this patch is that the rest transport will finally have an options object, which we need for other features anyway, e.g. to add an option for disabling error stack traces.

[raymondfeng]

@fabien Can you rebase?

[fabien]

@raymondfeng rebased (sorry for the double commit there)

[raymondfeng]

Any objections if I merge it?

[bajtos]

Any objections if I merge it?

I don't have any objections.