Feature/frontend UI layout#7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Descrição
Este Pull Request implementa a estrutura visual base da aplicação, incluindo os componentes de layout globais, estilização base e o mecanismo de proteção de rotas para a área administrativa.
Mudanças Realizadas
A implementação foca na fundação da interface do usuário:
1. Global Styles & Entry Point (
App.jsx,main.jsx,index.css)main.jsxcom o Provider do Redux e oBrowserRouter.App.jsxcom a definição central das rotas da aplicação.index.csscom as diretivas do Tailwind e estilos base de tipografia.2. Layout Shell (
Navbar,Footer,Layout)Navbarresponsiva com links de navegação.Footercom informações de rodapé.Layoutpara encapsular as páginas e manter a consistência visual em todo o site.3. Route Security (
ProtectedRoute)ProtectedRouteque verifica a existência de um token JWT e a role do usuário (OWNER) antes de permitir o acesso às rotas de administração.Decisões de Arquitetura
Layoutcomo wrapper para evitar repetição de código (Navbar/Footer) em cada página.react-router-dom.✅ Checklist