-
Notifications
You must be signed in to change notification settings - Fork 5
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
Issue 7 - Navbar #31
base: main
Are you sure you want to change the base?
Issue 7 - Navbar #31
Conversation
components/petdex/Navbar/Navbar.tsx
Outdated
<div | ||
className={`${!isOpen ? '' : 'left-[-400px]'} absolute flex flex-col left-0 top-[8rem] lg:relative lg:left-0 lg:top-0 `} | ||
> |
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.
acho que essa abordagem não é a das melhores usando tailwind, bom utilizar clsx/tailwindmerge - tem um link para referência e ele está no repo
além do position mudar de acordo com o tamanho da tela, não me parece certo
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.
Vou le esse artigo, valeu
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.
é bom criar tipagem para todas as props de componente, é valido dar uma olhada no seu lint
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.
outro ponto valido, será que vale a pena colocar a responsabilidade de renderizacao pra dentro do componente?
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.
" ...responsabilidade de renderizacao pra dentro do componente", acha melhor fragmentar em outro component ?
era uma abordagem que ia fazer mas pensei que colocar a renderizacao dentro dele seria melhor, pelo contexto e tals, mas pode ser, eu fragmento ele em 2 e uso a logica de renderizacao no nav, por exemplo:
{ !isSerarch
? <Logo />
: <LogoWithoutText />
}
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.
essa logica deveria estar no componente pai, que é responsavel pela renderizacao dele
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.
será que vale a pena colocar a responsabilidade de renderizacao pra dentro do componente?
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.
Muito bom ver você codando em tudo, da uma olhada nos coments, e padroniza os arquivos(components) para PascalCase
atualiza a branch! |
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.
ci/cd bb
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
Closes #7
Feature
Criar Navbar do Site Petdex
Solution
Checklist
Additional info