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

feat: new navigation with NavBar #32382

Draft
wants to merge 38 commits into
base: develop
Choose a base branch
from
Draft

feat: new navigation with NavBar #32382

wants to merge 38 commits into from

Conversation

juliajforesti
Copy link
Contributor

@juliajforesti juliajforesti commented May 7, 2024

SIDE-35

epic tasks:

Proposed changes (including videos or screenshots)

Issue(s)

Steps to test or reproduce

Further comments

Copy link
Contributor

dionisio-bot bot commented May 7, 2024

Looks like this PR is not ready to merge, because of the following issues:

  • This PR is missing the 'stat: QA assured' label
  • This PR is missing the required milestone or project

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

Copy link

changeset-bot bot commented May 7, 2024

⚠️ No Changeset found

Latest commit: ff82fff

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

codecov bot commented May 7, 2024

Codecov Report

Attention: Patch coverage is 71.07438% with 70 lines in your changes are missing coverage. Please review.

Project coverage is 51.51%. Comparing base (88d3114) to head (ff82fff).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop   #32382      +/-   ##
===========================================
- Coverage    56.36%   51.51%   -4.85%     
===========================================
  Files         2434     2155     -279     
  Lines        53693    48515    -5178     
  Branches     11050     9909    -1141     
===========================================
- Hits         30262    24993    -5269     
- Misses       20824    21257     +433     
+ Partials      2607     2265     -342     
Flag Coverage Δ
unit 72.99% <86.20%> (+0.68%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

<Box
ref={boxRef}
role='listbox'
// id={listId}
Copy link
Member

Choose a reason for hiding this comment

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

remove it, if it's useless

Copy link
Member

Choose a reason for hiding this comment

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

I would suggest creating a toolbar folder with these three toolbars separate, one file for each.
e.g NavBarPagesToolbar


type OmnichannelProps = Omit<HTMLAttributes<HTMLElement>, 'is'>;

export const NavBarItemOmnichannelContact = (props: OmnichannelProps) => {
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
export const NavBarItemOmnichannelContact = (props: OmnichannelProps) => {
export const NavBarItemOmnichannelContact = (props: Omit<HTMLAttributes<HTMLElement>, 'is'>) => {

import type { HTMLAttributes } from 'react';
import React from 'react';

type OmnichannelProps = Omit<HTMLAttributes<HTMLElement>, 'is'>;
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
type OmnichannelProps = Omit<HTMLAttributes<HTMLElement>, 'is'>;


type OmnichannelProps = Omit<HTMLAttributes<HTMLElement>, 'is'>;

export const NavBarItemOmnichannelQueue = (props: OmnichannelProps) => {
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
export const NavBarItemOmnichannelQueue = (props: OmnichannelProps) => {
export const NavBarItemOmnichannelQueue = (props: Omit<HTMLAttributes<HTMLElement>, 'is'>) => {


type DirectoryProps = Omit<HTMLAttributes<HTMLElement>, 'is'>;

export const NavBarItemDirectoryPage = (props: DirectoryProps) => {
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
export const NavBarItemDirectoryPage = (props: DirectoryProps) => {
export const NavBarItemDirectoryPage = (props: Omit<HTMLAttributes<HTMLElement>, 'is'>) => {

import type { HTMLAttributes, VFC } from 'react';
import React from 'react';

export const NavBarItemHomePage: VFC<Omit<HTMLAttributes<HTMLElement>, 'is'>> = (props) => {
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
export const NavBarItemHomePage: VFC<Omit<HTMLAttributes<HTMLElement>, 'is'>> = (props) => {
export const NavBarItemHomePage = (props: Omit<HTMLAttributes<HTMLElement>, 'is'>) => {


type MarketPlaceProps = Omit<HTMLAttributes<HTMLElement>, 'is'>;

export const NavBarItemMarketPlaceMenu = (props: MarketPlaceProps) => {
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
export const NavBarItemMarketPlaceMenu = (props: MarketPlaceProps) => {
export const NavBarItemMarketPlaceMenu = (props: Omit<HTMLAttributes<HTMLElement>, 'is'>) => {

Copy link
Member

Choose a reason for hiding this comment

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

I think we can throw this file in the trash 🗑️
its not being used since we're not going to have it under feature preview

@dougfabris
Copy link
Member

The NavBar alignment is different and kinda weird in the header of the pages in the mobile view

Screenshot 2024-05-29 at 16 31 59

@dougfabris
Copy link
Member

dougfabris commented May 29, 2024

Additionally, I found small issues using RTL language:

Kapture 2024-05-29 at 16 38 12

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.

None yet

2 participants