Skip to content

Conversation

@achrinza
Copy link
Member

@achrinza achrinza commented Aug 24, 2020

see: #5957

Signed-off-by: Rifa Achrinza 25147899+achrinza@users.noreply.github.com

Checklist

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

👉 Check out how to submit a PR 👈

@achrinza achrinza self-assigned this Aug 24, 2020
@achrinza achrinza added community-contribution Repository Issues related to @loopback/repository package labels Aug 24, 2020
@achrinza achrinza force-pushed the feat/filter-standalone branch from 6344a88 to 091407e Compare August 24, 2020 11:21
@achrinza achrinza requested a review from emonddr as a code owner August 24, 2020 11:21
@achrinza achrinza force-pushed the feat/filter-standalone branch 2 times, most recently from ef470fd to 7bbebea Compare August 24, 2020 12:36
@achrinza achrinza requested a review from nabdelgadir as a code owner August 24, 2020 12:36
@achrinza
Copy link
Member Author

The coverage drop doesn't seem to be related to this PR.

@achrinza
Copy link
Member Author

Thanks for the feedback, I agree with the points and applied them; PTAL.

@@ -0,0 +1,135 @@
# @loopback/filter
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which name is better?

  • @loopback/filter
  • @loopback/query-filter
  • @loopback/repository-filter

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer @loopback/filter as the filter is use both when working with queries and repositories. Prefixing it with query- or repository- may create confusion that the filter only applies when working with either one of those concepts.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good discussion!

I vote for @loopback/filter.

@raymondfeng
Copy link
Contributor

@achrinza Good initiative. The change LGTM. Let's settle on the name - https://github.com/strongloop/loopback-next/pull/6182/files#r477425945.

Copy link
Member

@bajtos bajtos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great initiative, @achrinza!

The code looks mostly good, I have one comment to address 👇🏻

Copy link
Contributor

@hacksparrow hacksparrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@achrinza achrinza force-pushed the feat/filter-standalone branch from 3979d5a to 794d8b8 Compare August 29, 2020 07:23
see: loopbackio#5957

Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
@achrinza achrinza force-pushed the feat/filter-standalone branch from 794d8b8 to dd012b3 Compare August 29, 2020 07:25
@achrinza achrinza requested a review from bajtos August 29, 2020 10:02
Copy link
Member

@bajtos bajtos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏🏻

@bajtos bajtos mentioned this pull request Sep 4, 2020
3 tasks
@achrinza achrinza merged commit f52d4df into loopbackio:master Sep 4, 2020
@achrinza achrinza deleted the feat/filter-standalone branch September 4, 2020 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Repository Issues related to @loopback/repository package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants