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

fix: ALPHA-4956 Time Range Hidden #392

Merged
merged 6 commits into from
Apr 10, 2024

Conversation

Xavier-Charles
Copy link
Contributor

@Xavier-Charles Xavier-Charles commented Apr 8, 2024

This also removes the bottom Navbar for Notifications, User Settings and Auth Pages as per design

Before

Screenshot 2024-04-08 at 14 25 28

After

Screenshot 2024-04-08 at 14 25 48

@Xavier-Charles Xavier-Charles marked this pull request as ready for review April 8, 2024 16:36
const isTabBarHidden = !!mobileRoutes.find(
(route) =>
route.type !== "fallback" &&
route.path === pathname &&
Copy link
Contributor

Choose a reason for hiding this comment

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

why are these 2 conditions neecessary, as opposed to just rely on the hideTabBar prop?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The hideTabBar Prop is not present in route options with type "fallback" because, they do not have a path prop to compare against and secondly are not the final route, they lead to other well defined route options

Copy link
Member

@elcharitas elcharitas Apr 9, 2024

Choose a reason for hiding this comment

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

Fallback routes are more less redirects. You should not need to hasndle the cases specifically since they would never display

I understand what you're trying to achieve. This works

Copy link
Contributor

@v-almonacid v-almonacid left a comment

Choose a reason for hiding this comment

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

Please test this thoroughly because routing has gave us a lot of headaches. Make sure you deploy this branch on epsilon and test when installed and not.

@Xavier-Charles Xavier-Charles marked this pull request as draft April 9, 2024 09:16
@Xavier-Charles Xavier-Charles marked this pull request as ready for review April 9, 2024 09:16
@@ -41,95 +41,108 @@ const CustomNavTab: React.FC<{
</div>
);

const RouterChild = () => {
Copy link
Member

Choose a reason for hiding this comment

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

Why not only extract out the TabBar?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There is this weird error when you extract just IonTabBar. It doesn't work
Screenshot 2024-04-09 at 12 28 48

Copy link
Member

@elcharitas elcharitas left a comment

Choose a reason for hiding this comment

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

Please extract only the affected component, IonTabBar

@elcharitas elcharitas self-requested a review April 9, 2024 11:32
Copy link
Member

@elcharitas elcharitas left a comment

Choose a reason for hiding this comment

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

I have doubts but lgtm

@Xavier-Charles Xavier-Charles merged commit 744d366 into dev Apr 10, 2024
4 checks passed
@Xavier-Charles Xavier-Charles deleted the fix/ALPHA-4956-Time-range-hidden branch April 10, 2024 05:17
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.

3 participants