-
Notifications
You must be signed in to change notification settings - Fork 16
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
305 navcomp refactoring #348
Conversation
Awesome work @san-oop! 🤩 Before diving into the code details, I have a few high level comments:
After this is taken care of, we can discuss the details of the implementation! 🙂 Thanks for taking this one on! 💯 |
Hi @san-oop! I've seen that there's a bug: when you try to scroll down, the app crashes. The bug is related to the Also, please don't forget to refactor the locale files too. Let me know if you need help with anything! 🙂 |
Fixes #305
The single big "NavigationBarAndDrawer" component is now refactored in to smaller sub components; It is mainly divided in to 3 more components
NavigationDrawer is designed in such a way that an array of menuitems is looped to get each menu item. So if a new menu item is required to be added in future, it is as easy by just adding a new object to this array of menuitems. (Menuitems is further divided in to 2, primary and secondary: refer the code in NavigationDrawer)
NavigationPopover This is not a generic popover component, and didnt find any particular code saving or code reusability if a generic one is implemented( MUI popover is more generic already). Hence this popover is exclusively designed to be shown in the app bar(for notifications)