-
Notifications
You must be signed in to change notification settings - Fork 18
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
changed from apolloclient to graphql-request #325
Conversation
✅ Deploy Preview for findadoc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
As a Junior I approve 👌
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.
b1fe24a
to
df486cb
Compare
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is telemetry?This package contains telemetry which tracks how it is used. Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked. What is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
The checks pass now. It is not resolving the duplicate locations still from what I see but I fixed the build problem I believe. I can remove those semicolons as well if they aren't supposed to be there. The problem was the yarn.lock needed to be rebuilt since since it was throwing errors for toUpperCase, and then the endpoint wasn't correct in the |
Just as a question. Does it resolve the bottom two issues as well or just the original one? |
I do not think this currently resolves the duplicate search results. I do not know what the best solution would be but I think if there is a script that creates a lookup like |
@NabbeunNabi that's a good question! we could solve in either the front end or backend. For now, I think front-end will be easier and should be fine for the result quantity. If it gets too heavy, we can shift to the backend. |
* docs: update README.md [skip ci] * docs: update .all-contributorsrc [skip ci] --------- Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
* docs: update README.md [skip ci] * docs: update .all-contributorsrc [skip ci] --------- Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
* docs: update README.md [skip ci] * docs: update .all-contributorsrc [skip ci] --------- Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
* fix: debug the ESLint config file Previously, the eslint file is not applying the linting and styling rules to our code * chore: format files with new linting rules * fixup! chore: format files with new linting rules --------- Co-authored-by: theyokohamalife <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* test: add tests for localeStore Previously, there were no tests present for the localeStore. In this commit I have created tests for localeStore * fixup! test: add tests for localeStore
This change adds the board members, developers and links to their linkedIn profiles for the ones that are currently available. There are tests for the additions as well. Changed the styling for the map container and main app in order to not have the footer cut through parts of the page.
ok everything is merged, working, CI builds, and ready for review again @theyokohamalife ! |
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 ✨ Thank you!
Resolves #369
Resolves #348
Resolves #366
What changed
Testing instructions