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: expose containerProps in StudioHeader [FC-0062] #529

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

rpenido
Copy link
Contributor

@rpenido rpenido commented Sep 5, 2024

Description

This PR adds a new boolean containerProps property to the StudioHeader component. This property will be passed downstream to the Container component in the Header, allowing the user to override the Container props (i.e. changing the max size).

More information

Part of:

Depends on:


Private ref: FAL-3820

@openedx-webhooks
Copy link

openedx-webhooks commented Sep 5, 2024

Thanks for the pull request, @rpenido!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently unmaintained.

To get help with finding a technical reviewer, tag the community contributions project manager for this PR in a comment and let them know that your changes are ready for review:

  1. On the right-hand side of the PR, find the Contributions project, click the caret in the top right corner to expand it, and check the "Primary PM" field for the name of your PM.
  2. Find their GitHub handle here.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Sep 5, 2024
Copy link

codecov bot commented Sep 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.55%. Comparing base (8213ee7) to head (10c3e12).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #529      +/-   ##
==========================================
+ Coverage   70.47%   70.55%   +0.08%     
==========================================
  Files          25       25              
  Lines         359      360       +1     
  Branches       94       95       +1     
==========================================
+ Hits          253      254       +1     
  Misses        104      104              
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -30,7 +30,7 @@ const NavDropdownMenu = ({

NavDropdownMenu.propTypes = {
id: PropTypes.string.isRequired,
buttonTitle: PropTypes.string.isRequired,
buttonTitle: PropTypes.node.isRequired,
Copy link
Contributor Author

@rpenido rpenido Sep 5, 2024

Choose a reason for hiding this comment

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

Not related to this feature. This is a fly-by fix of a console warning. Let me know if I should create a different PR for this.

@@ -110,6 +111,7 @@ const HeaderBody = ({
iconAs={Icon}
onClick={searchButtonAction}
aria-label={intl.formatMessage(messages['header.label.search.nav'])}
alt={intl.formatMessage(messages['header.label.search.nav'])}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not related to this feature. This is a fly-by fix of a console warning. Let me know if I should create a different PR for this.

Choose a reason for hiding this comment

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

Thanks for fixing these! Fewer warnings is always good.

@rpenido rpenido changed the title feat: allow full width header feat: allow full width header [FC-0062] Sep 6, 2024
Copy link

@pomegranited pomegranited left a comment

Choose a reason for hiding this comment

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

@rpenido Some comments for you -- and I still need to test this :)

@@ -110,6 +111,7 @@ const HeaderBody = ({
iconAs={Icon}
onClick={searchButtonAction}
aria-label={intl.formatMessage(messages['header.label.search.nav'])}
alt={intl.formatMessage(messages['header.label.search.nav'])}

Choose a reason for hiding this comment

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

Thanks for fixing these! Fewer warnings is always good.

@@ -37,6 +37,7 @@ const HeaderBody = ({
mainMenuDropdowns,
outlineLink,
searchButtonAction,
full,

Choose a reason for hiding this comment

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

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: f6673e9

src/studio-header/HeaderBody.jsx Outdated Show resolved Hide resolved
Copy link

@pomegranited pomegranited left a comment

Choose a reason for hiding this comment

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

👍

@@ -37,6 +37,7 @@ const HeaderBody = ({
mainMenuDropdowns,
outlineLink,
searchButtonAction,
fullWidth,
Copy link
Member

Choose a reason for hiding this comment

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

[consideration] I wonder if it'd make sense to expose a containerProps prop to use as a pass-thru with prop spreading, e.g. <Container size="xl" {...containerProps} />, where it'd stay default to xl but allow consumers reset size back to undefined. This would also give consumers more control to use any of the supported sizes beyond just xl and undefined, e.g. <StudioHeader containerProps={{ size: undefined }} />, <StudioHeader containerProps={{ size: 'lg' }} />. It would also let consumers change other Container props, like fluid per their use cases, e.g. <StudioHeader containerProps={{ fluid: false }} />.

If doing something like containerProps, we'd likely want to merge the containerProps.className with the existing className="px-2.5" on the Container component, e.g. with classNames:

const { containerProps } = props;
const { className: containerPropsClassName, ...restContainerProps } = containerProps || {};

<Container
  size="xl"
  className={classNames('px-2.5', containerPropsClassName)}
  {...restContainerProps}
>
  Hello world
</Container>

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I like the flexibility we would have if we allowed the developer to override the containerProps, but I'm also happy with the abstraction we have here.

Making the ContainerProps explicitly part of the header will tie us to the Container component, and we will have some compatibility issues in the event (very unlikely?) of replacing it in the future.

So I'm divided here, but happy with any path we go.

What are your thoughts @adamstankiewicz?
Do you mind giving us help @pomegranited here?

Choose a reason for hiding this comment

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

I like @adamstankiewicz 's idea here and for the footer.. could mean fewer PRs to these repos in future :)

@adamstankiewicz
Copy link
Member

[inform] It looks like the example MFE application in this repo is broken on the latest version of @openedx/frontend-build, i.e. running npm start results in a blank screen running on localhost:8080. See this PR for a fix to get the example running again, which should make local development within this repo easier by relying on the example app: #531

@rpenido rpenido marked this pull request as ready for review September 11, 2024 18:29
@rpenido rpenido force-pushed the rpenido/fal-3820-allow-full-width-header branch 3 times, most recently from 8741d1b to 192adc7 Compare September 18, 2024 21:51
@rpenido rpenido force-pushed the rpenido/fal-3820-allow-full-width-header branch from 192adc7 to ce107bf Compare September 18, 2024 21:54
@rpenido rpenido changed the title feat: allow full width header [FC-0062] feat: expose containerProps in StudioHeader [FC-0062] Sep 18, 2024
@@ -53,6 +54,7 @@ StudioHeader.propTypes = {
number: PropTypes.string,
org: PropTypes.string,
title: PropTypes.string.isRequired,
containerProps: HeaderBody.propTypes.containerProps,

Choose a reason for hiding this comment

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

containerProps should be optional, and/or populated with a default value below?

Copy link
Contributor Author

@rpenido rpenido Sep 19, 2024

Choose a reason for hiding this comment

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

Fixed here: e2249b2

@rpenido rpenido force-pushed the rpenido/fal-3820-allow-full-width-header branch from 41d76cc to 836e8a7 Compare September 19, 2024 20:01
@mphilbrick211 mphilbrick211 added the FC Relates to an Axim Funded Contribution project label Sep 19, 2024
@rpenido rpenido force-pushed the rpenido/fal-3820-allow-full-width-header branch from 836e8a7 to b54ec5a Compare September 19, 2024 20:55
@rpenido rpenido force-pushed the rpenido/fal-3820-allow-full-width-header branch from b54ec5a to e2249b2 Compare September 19, 2024 21:02
Copy link

@pomegranited pomegranited left a comment

Choose a reason for hiding this comment

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

👍 This looks and works well, thank you for taking the extra time here @rpenido !

package.json Outdated
@@ -38,7 +38,7 @@
"@edx/frontend-platform": "8.1.1",
"@edx/reactifex": "^2.1.1",
"@openedx/frontend-build": "14.1.2",
"@openedx/paragon": "22.7.0",
"@openedx/paragon": "22.8.0",

Choose a reason for hiding this comment

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

Should this mirror StudioFooter's dependency?

Suggested change
"@openedx/paragon": "22.8.0",
"@openedx/paragon": ">= 21.11.3 < 23.0.0",

Copy link
Contributor Author

@rpenido rpenido Sep 20, 2024

Choose a reason for hiding this comment

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

Good catch @pomegranited!
The version was wrong in both!
We need paragon 22.8.0 or upper here, so it should be ^22.8.0. We don't need the < 23.0.0 part because the ^ would not allow updates to major versions.

Fixed here: 35c2040

@rpenido rpenido force-pushed the rpenido/fal-3820-allow-full-width-header branch from 6658ec5 to 35c2040 Compare September 20, 2024 13:50
@@ -38,7 +38,7 @@
"@edx/frontend-platform": "8.1.1",
"@edx/reactifex": "^2.1.1",
"@openedx/frontend-build": "14.1.2",
"@openedx/paragon": "22.7.0",
"@openedx/paragon": "^22.8.0",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think we need paragon in the devDependencies, but I'm keeping it

@rpenido
Copy link
Contributor Author

rpenido commented Sep 20, 2024

Hi @adamstankiewicz! Could you do a review/merge here when you have some time? Thank you!

@bradenmacdonald
Copy link

@adamstankiewicz we need to ship some features that this is blocking - did you have any further concerns here? If your plate is full I can do a review+merge - but I just want to make sure you don't have any unaddressed concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FC Relates to an Axim Funded Contribution project open-source-contribution PR author is not from Axim or 2U
Projects
Status: Waiting on Author
Development

Successfully merging this pull request may close these issues.

6 participants