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

Search #206

Merged
merged 9 commits into from
Nov 10, 2021
Merged

Search #206

merged 9 commits into from
Nov 10, 2021

Conversation

ascampos
Copy link

@ascampos ascampos commented Nov 2, 2021

Screen Shot 2021-11-02 at 6 55 40 PM

Screen Shot 2021-11-02 at 6 57 06 PM

@ascampos
Copy link
Author

ascampos commented Nov 2, 2021

#131

@alexjball alexjball linked an issue Nov 2, 2021 that may be closed by this pull request
Copy link
Member

@alexjball alexjball left a comment

Choose a reason for hiding this comment

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

Looking Great, Arturo! No idea why such a big diff in the yarn.lock 😂 do you use yarn? what version?

@@ -1,16 +1,17 @@
import { useState } from "react"
import React from "react"
Copy link
Member

Choose a reason for hiding this comment

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

Next.js automatically imports React for tsx files so we can remove this line

@@ -32,17 +32,17 @@ export function useAuth() {
*/
export function requireAuth(Component: () => JSX.Element) {
Copy link
Member

Choose a reason for hiding this comment

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

I think we can revert this file

@@ -0,0 +1,83 @@
import React from "react"
Copy link
Member

Choose a reason for hiding this comment

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

Next requires ever file under pages to be a routable page (that's why the frontend checks are failing), so why don't we create a compositions/search folder and move this and the css there, then update the import in search/index.

async function onSubmit(formValues: any) {
setLoading(true)
try {
// TODO
Copy link
Member

Choose a reason for hiding this comment

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

Take a look at the temporary UI for how to make the API call

@edward-malouf edward-malouf added this to the Search function UI milestone Nov 9, 2021
@ascampos ascampos marked this pull request as ready for review November 9, 2021 23:10
@github-actions
Copy link

github-actions bot commented Nov 9, 2021

Visit the preview URL for this PR (updated for commit ascampos/police-data-trust@b4d92d8):

https://police-data-trust-dev--pr206-search-p8sml42g.web.app

(expires Wed, 17 Nov 2021 15:02:59 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 89ee28768ddf114979e2cf8eddd3746214cf93af

@ascampos
Copy link
Author

ascampos commented Nov 9, 2021

@alexjball I addressed your comments, but still not sure why there's such a large diff on yarn.lock im using v1.22.10

Copy link
Member

@alexjball alexjball left a comment

Choose a reason for hiding this comment

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

🔥 ! Most folks use npm which tries to update yarn.lock, but apparently not well enough!

@alexjball alexjball merged commit 60337dc into codeforboston:main Nov 10, 2021
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

Successfully merging this pull request may close these issues.

[FEATURE] create Search Panel component
3 participants