loopback-component-explorer | Browse and test your LoopBack app 's APIs | Socket library

1. First, you'll have to connect your app to the SQL datasource. Reference: https://loopback.io/doc/en/lb2/Connecting-models-to-data-sources.html

2. You'll have to manage ACLs for your "User Model". Reference : https://loopback.io/doc/en/lb2/Controlling-data-access.html

   1. Then you can create and get listed users based on the ACLs you've defined for your user model.

Since you are upgrading many dependencies to a higher semver-major version, you need to deal with breaking changes introduced in those versions.

LoopBack provides a migration guide for developers upgrading from 2.x to 3.x, see https://loopback.io/doc/en/lb3/Migrating-to-3.0.html.

Error: Cannot resolve path "loopback/server/middleware/compress"

LoopBack 3.x upgraded Express from 2.x to 3.x (IIRC) and as a result, popular middleware is no longer bundled - applications have to install and load them explicitly.

I see that you already have compression listed in your dependencies, so now you need to change the code calling require('loopback/server/middleware/compress') to call require(compression') instead. Check also your server/middleware.json file, LoopBack applications usually configure middleware through that config file.

"loopback-datasource-juggler": "^4.6.2",

In LoopBack 3.0, we moved loopback-datasource-juggler from peerDependencies to regular dependencies, LoopBack applications are no longer depending on juggler directly. Please remove this entry from your package.json.

See https://loopback.io/doc/en/lb3/Migrating-to-3.0.html#edit-packagejson and https://loopback.io/doc/en/lb3/3.0-Release-Notes.html#loopback-datasource-juggler-is-now-a-regular-dependency-of-loopback

I'm going to assume Clients is your extension model for the Users model. If this is the case, the Clients/reset endpoint of the API accepts an inline object with one property of 'email'.

So, in your case, you need to change your resetPwd method to reflect this, ie:

I was able to create the model with lb model selecting the datasource for storage.

Then the rest apis are provided.

The find method is asynchronous and returns a Promise. Actually, your code

console.log("resultList: " + resultList.value );

is always executed before this block:

Try adding:

For loopback-connector-db2, you must define SCHEMA in the datasources.json config file.

So I have realized that it was in fact gzipping it. I was running the curl -I --compress command which just makes a HEAD request. Since there is no body to compress, it will not add the header. Instead use the curl -is --compress command so that you can see if it is compressing the body or not.

You need to tell the compression module that those files are compressible. You can define a filter method in the compression options object.

filter

A function to decide if the response should be considered for compression. This function is called as filter(req, res) and is expected to return true to consider the response for compression, or false to not compress the response.

The default filter function uses the compressible module to determine if res.getHeader('Content-Type') is compressible.