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

196 as a dev I want to refactor the header component #297

Merged
merged 31 commits into from
Oct 30, 2024

Conversation

SamuelPelletierEvraire
Copy link
Contributor

@SamuelPelletierEvraire SamuelPelletierEvraire commented Oct 24, 2024

- Created User class file (Base)
- Implement header component.
- Remove some console.log unused in layout.tsx
- Add userPopUp component (Not finish yet)
- Added user class to manage user information
- Added UserPopup.tsx for log out/ version app / username
- Added theme.d.ts file to add additional type for theme
- Add new new type (Breakpoints)
- Remove file counter.tsx that was not used (Exemple case)
- Fix lint
- Fix ACIA logo adaptiveness
- Create file for test Header
k-allagbe

This comment was marked as resolved.

k-allagbe

This comment was marked as resolved.

@SamuelPelletierEvraire
Copy link
Contributor Author

Animations like loading indicators are necessary however.
@k-allagbe
This is gonna be made in another Issue about skeleton loading

@SamuelPelletierEvraire
Copy link
Contributor Author

Create new issue : Create new issue for separate user Popup and the header.: #298

export default function RootLayout({
children,
}: Readonly<{ children: React.ReactNode }>) {
const [SideNavOpen, setSideNavOpen] = useState(false);
const { sideNavOpen } = useStore();
Copy link
Member

Choose a reason for hiding this comment

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

Let's use the zustand stores sparsely. As a rule of thumb, when the components sharing the state are grouped and hierarchically not too distant, we should use useState and props drilling. Like in this case with Header and SideNav, they are close enough, using useState is fine.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@ChromaticPanic
Copy link
Contributor

ChromaticPanic commented Oct 24, 2024

It's doing a weird horizontal scroll thing on the sidenav . Left Bottom.
Also the vertical scrollbar persists no matter the browser height

image

image

@SamuelPelletierEvraire
Copy link
Contributor Author

It's doing a weird horizontal scroll thing on the sidenav . Left Bottom. Also the vertical scrollbar persists no matter the browser height

image

image

The side nav was already implemented but not done at all gonna be done in other issue.

@k-allagbe k-allagbe merged commit 965c106 into main Oct 30, 2024
6 checks passed
@SamuelPelletierEvraire SamuelPelletierEvraire deleted the 196-as-a-dev-i-want-to-refactor-the-header-component branch December 19, 2024 17:41
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.

As a dev, I want to refactor the header component
4 participants