Skip to content
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

[BB pr#2] KIT-3 Configure Snyk #2

Closed
coveobot opened this issue Apr 2, 2020 · 5 comments
Closed

[BB pr#2] KIT-3 Configure Snyk #2

coveobot opened this issue Apr 2, 2020 · 5 comments
Assignees

Comments

@coveobot
Copy link
Contributor

coveobot commented Apr 2, 2020

Pull request 🔀 created by @ThibodeauJF on 2020-04-02 17:59
Last updated on 2020-04-04 00:23
Original Bitbucket pull request id: 2

Participants:

Source: Commit 3af766e94fd7 on branch KIT-3> Destination: https://bitbucket.org/coveord/ui-kit/commits/3e6d468fd902 on branch master
Merge commit: https://github.com/None/commit/ef28b5d15dc1

State: MERGED

Checkout the headless project on Snyk: https://app.snyk.io/org/coveo-jsui/

https://coveord.atlassian.net/browse/KIT-3

@coveobot
Copy link
Contributor Author

coveobot commented Apr 3, 2020

@olamothe commented on 2020-04-03 12:54

Outdated location: line 39 of .deployment.config.json

So, I was wondering if we’d want to scan the root package.json file, since it only contains dev dependencies/lib that we use as “tooling” to help us develop/deploy etc.

My understanding is that, with lerna, the only things that will ever be included in the top package.json file will always be “dev dependencies”. Is that a fair assumption ? And so we’d only want to scan/test the subpackages.

I’ve asked in slack (#support-dev-tooling) to make sure.

Edit: And in that case, can we put “packages/*” or something like that ?

@coveobot
Copy link
Contributor Author

coveobot commented Apr 3, 2020

@olamothe approved ✔️ the pull request on 2020-04-03 12:54

@coveobot
Copy link
Contributor Author

coveobot commented Apr 3, 2020

@olamothe commented on 2020-04-03 13:38

Outdated location: line 39 of .deployment.config.json

Yep, confirmed, we don’t need to check licenses for build tool/library only.

@coveobot
Copy link
Contributor Author

coveobot commented Apr 3, 2020

@samisayegh approved ✔️ the pull request on 2020-04-03 13:40

@coveobot
Copy link
Contributor Author

coveobot commented Apr 3, 2020

@btaillon approved ✔️ the pull request on 2020-04-03 17:03

SimonMilord added a commit that referenced this issue Jan 22, 2024
…e Search Box components #2 (#3501)

* created quanticSearchBoxInput with customEvents, cleaned up standalone and default searchbox

* some more improvements

* fixed events, styling, need to fix submit search

* fix issues and clean logs

* fixed e2e tests

* some cleanup

* added rough structure of UTs (to finish)

* added unit tests, still need some work

* added some improvements, some tests still failing

* set custom event names to lowercase

* modified events in uts

* added commands for unit tests in the README file

* fixed and cleanup unit tests for searchboxinput

* fixed linter issue with test

* try to fix linter fail

* added unit tests for withoutSubmitButton

* fix bug display of searchbox when expandable and withoutSubmitButton is true

* fix icon sliding issue in expandable searchbox

* added feedback improvements

* fixed bug where pressing enter on clear button was not working for standalone searchbox

* Revert "added feedback improvements"

This reverts commit 965b011.

* Revert "Revert "added feedback improvements""

This reverts commit 35dd5d8.

* Revert "fixed bug where pressing enter on clear button was not working for standalone searchbox"

This reverts commit e89a138.

* refactored aria-labelledBy

* removed useless aria value

* added some improvements
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants