-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[FullscreenBar] Add this component for use in Fullscreen apps #5688
Conversation
size-limit report 📦
|
82d8495
to
be1bb0e
Compare
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.
Couple of comments but this is looking good 👍
polaris-react/src/components/FullscreenBar/tests/FullscreenBar.test.tsx
Outdated
Show resolved
Hide resolved
I wanted to ask your advice on a larger question about this component in relation to |
0081c22
to
f0057c2
Compare
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.
Almost good to go but would like some more eyes if we can get them. Going to request @jjgali for content as well
polaris-react/src/components/FullscreenBar/tests/FullscreenBar.test.tsx
Outdated
Show resolved
Hide resolved
## Related components | ||
|
||
- To provide quick, at-a-glance feedback on the outcome of an action, use the [toast](https://polaris.shopify.com/components/feedback-indicators/toast) component. | ||
- To indicate to merchants that a page is loading or an upload is processing use the [loading](https://polaris.shopify.com/components/feedback-indicators/loading) component. |
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.
Add comma after "processing":
To indicate to merchants that a page is loading or an upload is processing, use the ...
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.
Left a few comments—I think the main things we'll want to fix, content wise, are references to the top bar
component that got copied over, as well as the main description. I think we should rewrite it so it's not a direct copy of the top bar description.
Happy to take another look when you're ready!
Thanks for the great review! Sorry I flubbed on the README. Dang. OK, I've fixed the references. Please take another look at your leisure. |
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.
Changes look great on my end! Also fixed a few tiny grammar/punctuation things in the readme directly, if that's okay.
Thank you! Yeah, that's great and much appreciated. 😄 |
Hey folks-- Are there more reviews required for this to go through? Looks like several people are assigned. I'll rebase today, but the conflict looks constrained to UNRELEASED.md, so no functionality differences. Thanks in advance!! |
- global chrome | ||
- global features |
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.
Just wondering if this is truly global. We may want to omit these since they're not used on every page in the admin
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.
Actually there are probably a few more here that should be removed as well since they're not directly related to this component:
- nav bar
- navbar
- brand
- search
- user
- menu
- logo
Can probably all be removed
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.
👍
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.
Fixed, thanks!! Yeah, I really wasn't sure what was right there, so this really helps.
|
@kyledurand : There's a changeset-bot that's recommending I add one. But it looks like we add an entry to the If that's all good, is this good to merge now? 😄 |
@camd Ignore the changeset for now |
🚀 |
403a9d3
to
34aaa01
Compare
@camd we have shipped changeset now. Please run |
abf27e9
to
4c42ad9
Compare
🎉 Thanks for your contribution to Polaris! |
WHY are these changes introduced?
Fixes #5664
We are rolling out Fullscreen mode in Apps (first and third-party) in App Bridge. We want to give App developers an easy way to be conformant with our requirements on Fullscreen. If they are in that mode, they MUST provide a navigation bar with a back button to exit.
WHAT is this pull request doing?
This PR adds a top bar with uniformed styling on a Back button to exit Fullscreen mode. It can contain children so that the App developer can customize the rest of the bar to their needs.
How to 🎩
🖥 Local development instructions
🗒 General tophatting guidelines
📄 Changelog guidelines
You can test this component locally in Storybook:
Fullscreen bar
or in a Spin instance: https://shop1.shopify.fsbar.cameron-dawson.us.spin.dev/admin/email_templates/order_confirmation/edit
🎩 checklist
README.md
with documentation changes