-
Notifications
You must be signed in to change notification settings - Fork 26
feat: pass pluginProps to wrapper
#118
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: pass pluginProps to wrapper
#118
Conversation
|
Thanks for the pull request, @rpenido! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo 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:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere 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:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
1 similar comment
|
Thanks for the pull request, @rpenido! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo 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:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere 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:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #118 +/- ##
=======================================
Coverage 95.91% 95.91%
=======================================
Files 10 10
Lines 245 245
Branches 75 72 -3
=======================================
Hits 235 235
Misses 9 9
Partials 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
674cdbc to
797e0df
Compare
797e0df to
ab13fc4
Compare
arbrandes
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks eminently reasonable, but I'm concerned about backward compatibility. Do you mind adding unit tests that verify that not having any pluginProps specified both in the slot itself and in the user-provided wrapper won't break anything?
src/plugins/data/utils.jsx
Outdated
| * | ||
| * @param {Function} renderComponent - Function that returns JSX (i.e. React Component) | ||
| * @param {Array} wrappers - Array of components that each use a "component" prop to render the wrapped contents | ||
| * @params {object} pluginProps - Props defined in the PluginSlot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this is a typo:
| * @params {object} pluginProps - Props defined in the PluginSlot | |
| * @param {object} pluginProps - Props defined in the PluginSlot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Fixed here: 97f0e24
README.rst
Outdated
| pluginProps: { | ||
| prop1: 'prop1', | ||
| }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this works. The only way to pass pluginProps is via the slot instance itself, not via env.config.jsx.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ops! My bad. Fixed here: 97f0e24
arbrandes
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I think this is good. Thank you for your patience!
|
🎉 This PR is included in version 1.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
Thanks for the review and merge @arbrandes! |
Description
In this PR, we add support to read the
pluginPropsusing thePLUGIN_OPERATIONS.Wrapoperation. This gives us more flexibility while using plugins, allowing the wrapper component to receive context from thePluginSlot.There is a practical use here: openedx/frontend-plugin-aspects#115
Additional Information
Testing Instructions
Private ref: FAL-4299