LoopBack makes it easy to build modern API applications that require complex integrations.

This issue is for new folks to chime in and say hello and that they'd like to be involved offline (off GitHub) discussions. I'm not expecting the working group on this project to be so large that we can't all get to know each other.

Just comment here that you'd like to be added to the LoopBack.next contributors list and I'll create a group in the StrongLoop org with all of you - so we can do things like @strongloop/loopback-next for scheduling external meetings and such.

When we invite you to join our org and you don't receive an email notification for GitHub, then you can accept the invite here: https://github.com/strongloop

Check out issues labelled as good first issue for tasks suitable for new contributors.

Updated on 05/31/2019

Hi all! First of all, thanks for your interests and support in LoopBack 4!

We have been thinking about how to grow our contributor community together with the user community. There are several ways to contribute:

• Provide your feedback We'd love to hear your feedback! Feel free to comment on the GitHub issues that interest you or open an issue in this repo
• Contributing code Please see below for details. For step-by-step instructions in submitting a PR, refer to https://loopback.io/doc/en/lb4/submitting_a_pr.html.
• Contributing docs From the feedback we got, there's a need to improve our docs. This PR outlines some of the enhancements we'd like to make: https://github.com/strongloop/loopback-next/pull/2925

Contributing code

Contribute what you need

We hope you are contributing to something that you need or will be using. We'd encourage you to take a backlog and see if any of our GitHub issues capture your requirement. If you're planning to implement a more complex feature, it would be helpful to submit a draft PR with minimal implementation to discuss your approach first. It would also be helpful to include your use case so that we can understand your requirements better. This is to make sure the intended implementation would align with our architecture and direction.

Contribute anything

If you don't have a particular area you want to contribute, you can look up the help wanted: https://github.com/strongloop/loopback-next/labels/help%20wanted

New Contributors?

If you're new to contributing to LoopBack or open source projects in general, don't worry. You can look at issues with good first issue. Those issues are meant for new contributors: https://github.com/strongloop/loopback-next/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22

This pull request attempts to set up the hasManyThrough relation using the hasMany relation. It does it using a through property that can be provided to the @hasMany() decorator.

I chose to setup the hasManyThrough this way in an attempt to stick to the existing loopback hasManyThrough spec.

https://loopback.io/doc/en/lb3/HasManyThrough-relations.html#defining-a-hasmanythrough-relation

import { Entity, model, hasMany, property } from '@loopback/repository';
import { Patient, Appointment } from '../models';

@model()
export class Physician extends Entity {
  @property({
    type: 'string',
    id: true
  })
  id?: string;

  @hasMany(() => Patient, { through: () => Appointment })
  patients: Patient[];
}

See also #2264 See also #2356

Checklist

• [x] npm test passes on your machine
• [x] New tests added or existing tests modified to cover all changes
• [x] Code conforms with the style guide
• [x] API Documentation in code was updated
• [x] Documentation in /docs/site was updated
• [x] Affected artifact templates in packages/cli were updated
• [x] Affected example projects in examples/* were updated

i want implement socket in my loopback4 server API. i have integrate socket in my API but it;s routing is not working.

app.io = require('socket.io')(await app.start());
  app.io.on('connection', async function (socket: any) {

    console.log('connected', socket.id)
    socket.on('disconnect', function () {
      console.log('user disconnected');
    });
  });

it's my code but socket is not connected. i have seen this example.

https://github.com/raymondfeng/loopback4-example-websocket/ but it's work only socket server not working with API server. please suggest me how i can implement.

A list of potential extensions for LoopBack Next.

Add a 👍 reaction to any of the comments below if you are interested in seeing these features / extensions

Description / Steps to reproduce / Feature proposal

Follow up task for PR #1342

Inclusion of related models (same as LB3) For example, Customer model has {include: ['order']}. When query on Customer, the result should includes the Order array.

Duplicates:

• Include related models in "GET /mymodels" results #1889
• https://stackoverflow.com/questions/53162562/loopback-4-hasmany-include-filter-error-500/53172949

Follow-up stories:

• Add support for "include" and "fields" to findById (REST API) #1721

Acceptance Criteria

MVP scope

2019Q3

• [x] Add keyFrom to resolved relation metadata #3441
• [x] Test relations against databases #3442
• [x] Add findByForeignKeys helper (initial version) #3443
• [x] Introduce InclusionResolver concept #3445
• [x] Include related models in DefaultCrudRepository #3446
• [x] Implement InclusionResolver for hasMany relation #3447
• [x] Implement InclusionResolver for belongsTo relation #3448
• [x] Implement InclusionResolver for hasOne relation #3449
• [x] Update todo-list example to use inclusion resolver #3450

2019Q4

• [x] Reject create/update requests when data contains navigational properties #3439
• [x] Add inclusion resolvers to lb4 relation CLI #3451
• [x] Verify relation type in resolve{Relation}Metadata #3440
• [x] Run repository tests for PostgreSQL #3436
• [x] Run repository tests for Cloudant #3437
• [x] Blog post: announce Inclusion of related models #3452

Out of MVP scope

• [ ] Support inq splitting in findByForeignKeys #3444
• [x] Include related models with a custom scope #3453
• [ ] Recursive inclusion of related models #3454
• [ ] Reject queries with incompatible "filter.fields" and "filter.include" #3455
• [ ] Spike: robust handling of ObjectID type for MongoDB #3456

See https://github.com/strongloop/loopback-next/issues/3585 for the full list.

Initial implementation of a Phase based Booter in Application as well as a @loopback/boot package to contain booters.

implements #780

Checklist

• [x] npm test passes on your machine
• [x] New tests added or existing tests modified to cover all changes
• [x] Code conforms with the style guide
• [x] Related API Documentation was updated
• [x] Affected artifact templates in packages/cli were updated
• [x] Affected example projects in packages/example-* were updated

Description

I'm using LB4 with PostgreSQL DataSource. Currently I have 36 models with multiple relations between them. Throws the following warning

(node:39148) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 connected listeners added. Use emitter.setMaxListeners() to increase limit

setup

"dependencies": {
    "@loopback/boot": "^1.0.7",
    "@loopback/context": "^1.3.0",
    "@loopback/core": "^1.1.2",
    "@loopback/openapi-v3": "^1.1.4",
    "@loopback/repository": "^1.1.0",
    "@loopback/rest": "^1.5.0",
    "@loopback/rest-explorer": "^1.1.3",
    "@loopback/service-proxy": "^1.0.4",
    "loopback-connector-postgresql": "^3.5.0"
  }

As you might know already, we're wrapping up on the LoopBack4 Core Beta release.  We are now calling out to our LB community users (especially @strongloop/loopback-next) to develop LB extensions!  

How it works

Tell us

Let us know which extension you'd like to build.  Here is the wish list voted by the community: https://github.com/strongloop/loopback-next/issues/512. Examples of LB extensions: - Authentication: https://github.com/strongloop/loopback-next/tree/master/packages/authentication - Log extension: https://github.com/strongloop/loopback4-example-log-extension (currently in dev branch)

Build it

One of the LB project maintainers will be assigned to you to walk you through the whole journey of creating an extension from the beginning till the end.

Get recognized

We'll broadcast your work in our web site and social media!   For more information about LoopBack 4, please refer to: http://loopback.io/doc/en/lb4.

| Extension | Descriptions | Developers | LB4 Maintainer | ------------- |:-------------:| -----:|-----:| | GraphQL | Component to provide GraphQL Endpoint for Models. https://github.com/strongloop/loopback-next/issues/656 | @virkt25 , @mpicard, @beeman, Help Welcome | Taranveer (@virkt25) | |gRPC | https://github.com/strongloop/loopback-next/issues/675 | @jonathan-casarrubias, @VMois | @raymondfeng or @bajtos | |API Explorer | https://github.com/strongloop/loopback-next/issues/559 | @ssh24 |@b-admike | |MQTT | MQTT transport https://github.com/strongloop/loopback-next/issues/710 | @akashjarad, @Negrero | TBD

References

• Extension Starter: https://github.com/strongloop/loopback4-extension-starter

Steps to reproduce

At work we have started using Loopback with Mssql and today we have to connect with a view with 100 million records but I have encountered a problem ... Tedious is not able to process the request with filters or limit

Current Behavior

I am currently returning an error like this: ?filter[limit]=100: 500 RequestError: Timeout: Request failed to complete in 15000ms

Expected Behavior

I expected him to give me 100 records back, I don't expect them to ever return me, it's impossible in less than 15 seconds!

Additional information

darwin x64 13.1.0

├── @loopback/[email protected]
├── @loopback/[email protected]
├── @loopback/[email protected]
├── @loopback/[email protected]
├── @loopback/[email protected]
├── @loopback/[email protected]
├── @loopback/[email protected]
├── @loopback/[email protected]
├── @loopback/[email protected]
├── @loopback/[email protected]
└── [email protected]

Recreated from https://github.com/strongloop/loopback-next/pull/2111 due to branch renaming.

• ContextView - watches matching bindings of a context and maintain a live collection of values
• @inject.view - injects an array of values resolved from bindings that match the filter function
• Enhance @inject and @inject.getter to accept a binding filter function

See docs.

Checklist

• [x] npm test passes on your machine
• [x] New tests added or existing tests modified to cover all changes
• [x] Code conforms with the style guide
• [x] API Documentation in code was updated
• [x] Documentation in /docs/site was updated
• [ ] Affected artifact templates in packages/cli were updated
• [ ] Affected example projects in examples/* were updated

Implements:

• https://github.com/strongloop/loopback-next/issues/1845
• https://github.com/strongloop/loopback-next/issues/2034

The PR implements the following features:

• Allow registration and actions of life cycle observers using context bindings - See https://github.com/strongloop/loopback-next/blob/lifecycle/docs/site/Life-cycle.md
• Discover and boot life cycle scripts
• Add lb4 observer command to generate life cycle scripts - See https://github.com/strongloop/loopback-next/blob/lifecycle/docs/site/Life-cycle-observer-generator.md

Test observer cli

cd loopback-next
git checkout lifecycle
npm run build
cd sandbox
../packages/cli/bin/cli-main.js app life
cd life
../../packages/cli/bin/cli-main.js observer
cd ../..
npm i
cd sandbox/life
npm start

Checklist

• [x] npm test passes on your machine
• [x] New tests added or existing tests modified to cover all changes
• [x] Code conforms with the style guide
• [x] API Documentation in code was updated
• [x] Documentation in /docs/site was updated
• [x] Affected artifact templates in packages/cli were updated
• [ ] Affected example projects in examples/* were updated

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | ajv (source) | ^8.11.2 -> ^8.12.0 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

This PR adds implementation to controllers.

Signed-off-by: Muhammad Aaqil [email protected]

Checklist

• [x] DCO (Developer Certificate of Origin) signed in all commits
• [x] npm test passes on your machine
• [x] New tests added or existing tests modified to cover all changes
• [x] Code conforms with the style guide
• [x] API Documentation in code was updated
• [x] Documentation in /docs/site was updated
• [x] Affected artifact templates in packages/cli were updated
• [x] Affected example projects in examples/* were updated

👉 Check out how to submit a PR 👈

Describe the bug

npm test fails under packages/cli for one of the test scenarios. The reason for this test failing is the fact that $schema under tsconfig.json in the examples under the repository has the value: https://json.schemastore.org/tsconfig. While the examples available at npm registry has http://json.schemastore.org/tsconfig.

Logs

1) lb4 example
       removes project references from tsconfig:

      AssertionError: expected Object {
  $schema: 'http://json.schemastore.org/tsconfig',
  extends: '@loopback/build/config/tsconfig.common.json',
  compilerOptions: Object { outDir: 'dist', rootDir: 'src', composite: false },
  include: Array [ 'src/**/*', 'src/**/*.json' ]
} to equal Object {
  $schema: 'https://json.schemastore.org/tsconfig',
  extends: '@loopback/build/config/tsconfig.common.json',
  compilerOptions: Object { outDir: 'dist', rootDir: 'src', composite: false },
  include: Array [ 'src/**/*', 'src/**/*.json' ]
} (at $schema, A has 'http://json.schemastore.org/tsconfig' and B has 'https://json.schemastore.org/tsconfig')
      + expected - actual

       {
      -  "$schema": "http://json.schemastore.org/tsconfig"
      +  "$schema": "https://json.schemastore.org/tsconfig"
         "compilerOptions": {
           "composite": false
           "outDir": "dist"
           "rootDir": "src"
      
      at Assertion.fail (/***/loopback-next/packages/testlab/node_modules/should/as-function.js:275:17)
      at Assertion.value (/***/loopback-next/packages/testlab/node_modules/should/as-function.js:356:19)
      at /***/loopback-next/packages/cli/test/integration/generators/example.integration.js:125:33

Additional information

No response

Reproduction

https://github.com/loopbackio/loopback-next/tree/master/packages/cli

Signed-off-by: Muhammad Aaqil [email protected]

In case of a belongsTo relation, the openAPI docs show array in the responses for the route: /sourceModel/:{targetId}/targetModel. (e.g: /orders/1/customer.

The target instance will always be a single record in case of belongsTo relation. Hence the type should be object. This PR changes the type in the response (in openAPI docs) from array to object.

There is one thing though, the actual response of the API is actually an object - not an array.

Checklist

• [x] DCO (Developer Certificate of Origin) signed in all commits
• [x] npm test passes on your machine
• [x] New tests added or existing tests modified to cover all changes
• [x] Code conforms with the style guide
• [x] API Documentation in code was updated
• [x] Documentation in /docs/site was updated
• [x] Affected artifact templates in packages/cli were updated
• [x] Affected example projects in examples/* were updated

This PR contains the following updates:

| Update | Change | |---|---| | lockFileMaintenance | All locks refreshed |

🔧 This Pull Request updates lock files to use the latest dependency versions.

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Describe the bug

I was looking up an example of the REST connector and reached here. Though the example shows up under lb4 docs, the example is actually for lb3.

Is this somehow expected?

Logs

No response

Additional information

No response

Reproduction

https://loopback.io/doc/en/lb4/REST-connector-example.html