-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(search): Implement the search products #46
Conversation
85fc615
to
0514b85
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #46 +/- ##
==========================================
- Coverage 79.65% 79.55% -0.11%
==========================================
Files 64 65 +1
Lines 1057 1115 +58
Branches 149 163 +14
==========================================
+ Hits 842 887 +45
- Misses 215 225 +10
- Partials 0 3 +3 ☔ View full report in Codecov by Sentry. |
045c477
to
e201c78
Compare
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
10820488 | Triggered | Generic Password | a01d398 | test/product.test.ts | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
src/docs/products.ts
Outdated
export const searchParams = { | ||
properties: { | ||
type:"params", | ||
name: { | ||
type: "string" | ||
}, | ||
minPrice: { | ||
type: "number" | ||
}, | ||
maxPrice: { | ||
type: "number" | ||
}, | ||
category: { | ||
type: "string" | ||
}, | ||
} | ||
} | ||
|
||
export const getProducts = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you using this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I'm not using it. I forgot to delete
e201c78
to
ee03b6f
Compare
- Seller should allowed to search their own products - other users which are not seller should see all products [Delives #187419190]
ee03b6f
to
a01d398
Compare
feat(search): Implement the search products
What does this PR do ?
This PR focus on searching products where users can search different products depend on their preference and can retrieve precisely products based on their searches.
Description of the PR
How should this be manually tested?
What are the relevant pivotal tracker stories?
[Delivers #187419190]