* Fix crash when modifying an unknown user (Matheus Horstmann)
* test: fix User test for custom token generator (Miroslav Bajtoš)
* test: improve assertion error messages (Miroslav Bajtoš)
Fix AccessToken's method tokenIdForRequest to treat an empty string
as if no access token was provided.
This is needed to accomodate the changes made in
loopback-datasource-juggler@2.56.0.
Rework the REST middleware to use a hand-written version of
"async.eachSeries". Before this change, we were loosing CLS context
when the application was relying on the REST middleware to load the
context middleware.
This is fixing a problem introduced by post-1.0 versions of async,
which we upgraded to via fea3b781a.
Fix configuration of Karma:
- Disable ES6 modules. The ES6 module transpiler is adding
"use strict" to all source files, this breaks e.g. chai or juggler
- Relax "ignore" setting to exclude only strong-task-emitter,
thus bring back Babel transpilation for chai and juggler.
Before this change, dependencies in node_modules (e.g. strong-remoting)
were not transformed to ES5 and thus crashed the tests in PhantomJS.
Note that loopback-datasource-juggler cannot be babelified to ES5
because it does not correctly support strict mode yet.
* Drop support for Node.js versions 0.10 and 0.12 (Miroslav Bajtoš)
* test: fix too strict test assertion (Miroslav Bajtoš)
* Add unit test for empty password (loay)
* Update translated strings Q2 2017 (Allen Boone)
Some of our dependencies are no longer supporting pre-4.0 versions of
Node.js. As a result, our CI builds are failing on these platforms.
This pull request removes 0.10 and 0.12 from our Travis CI build matrix
and also adds "engines" field to package.json to tell our internal
Jenkins CI to stop testing 0.10 and 0.12 versions too.
Rework the test verifying properties of `loopback` to ignore
new express properties added after the test was written.
Ignore "json" and "urlencoded" middleware that was added back
to Express, keep using our wrappers printing a deprecation message.
Currently any `currentUserLiteral` routes when accessed with a bad
token throw a 500 due to a SQL error that is raised because
`Model.findById` is invoked with `id={currentUserLiteral}`
(`id=me` in our case) when the url rewrite fails.
This commit changes the token middleware to return 401 Not Authorized
when the client is requesting a currentUserLiteral route without
a valid access token.
jannyHou
Janny
Hage Yaapa
Diana Lau
Miroslav Bajtoš
Matheus Horstmann
andrey-abramow
virkt25
Kevin Delisle
Miroslav Bajtoš
Samuel Reed
Loay
Candy
Allen Boone
Aaron Buchanan