Rifa Achrinza

Thanks for applying the changes and sorry for the delayed review; Everything LGTM :+1: Just need to squash into a single Git Commit and it can be merged.

Transferred to `loopback-datasource-juggler` repo.

Thanks for the PR. In the future, consider updating the existing PR instead of opening new ones so that it's easier for the maintainers to follow and track. Thanks!

Thanks for the detailed report on the issue, @bmaupin! I've read through the other issue, and cross-checked with the source code here; It does seem that this package doesn't properly...

Hi @Doni1231, this Git Repository is for the old LoopBack 3 project and is not actively monitored. Please open an issue in https://github.com/loopbackio/loopback-next/issues for LoopBack 4-related bugs. For questions on...

Hi @nishankpathak, this repository is for LoopBack 3. Please create an issue or GitHub Discussion in https://github.com/loopbackio/loopback-next for LoopBack 4-related matters.

Hi @mercale, this repo is for the older EOLed **LoopBack 3** framework and isn't being actively monitored. LoopBack 4 is under https://github.com/strongloop/loopback-next. cc: @dhmlau could you assist in transferring this...

@emonddr, apologies if I wasn't clear - what I meant was the `order` **filter** that is passed to repository functions. This is added to the OpenAPI spec's expected request parameter...

@agnes512 Currently, the default parameter generated by the API Explorer is: ```json { "order": [ "string" ] } ``` While it does makes sense, it can't be used as-is as...

Apologies for the delayed reply, have you tried the following? ```ts this.employeeRepository.find({ fields: { empName: true, departmentId: true, location : true }, where: { location: { locality: {regexp: pattern} }...