-
Notifications
You must be signed in to change notification settings - Fork 2.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
React + SSR conversion of remaining components #2040
Labels
epic
For issues that exist only to track progress on a list of other issues in one place
Comments
This was referenced Mar 27, 2017
This was referenced Mar 28, 2017
This was referenced Jan 31, 2018
Closed
40 tasks
Issue moved to reactioncommerce/reaction-feature-requests #7 via ZenHub |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
React + SSR
This epic is meant to track the conversion of all customer / admin facing components, layouts, templates to React. This means no more Blaze wrappers around any react component, and no Blaze components at any point in the React layout tree. All react all the time.
Keep in mind, for SSR to work, no react component may access
document
orwindow
while being rendered server-side. If you need them, you'll need to check if they exists before trying to access.Below List in ordered by approximate priority
Router
ReactionLayout
should support react components / layouts if one is registered (PR React Router #2123) @mikemurrayLayout
coreAdminLayout
fromcoreLayout
(PR React Router #2123) @mikemurrayReact
version of ReactionLayout, used in the PDP page @mikemurrayNavigation bar
Product Grid
Search
ui-search
package)Checkout
Product Detail
Orders
Admin
template
while opening an ActionView, it will use the react component before falling back to a blaze template.)The text was updated successfully, but these errors were encountered: