Fractal: Changes needed to support React components properly

Created on 9 Mar 2016  路  7Comments  路  Source: frctl/fractal

  • [x] support non-component preview layouts. Reference by path?
  • [x] support for requireing and converting JSX files (https://babeljs.io/docs/usage/require/)
  • [x] defer rendering of preview layout to adapter, if renderLayout method is defined
  • [x] prevent .config.js files from being parsed as components
  • [ ] Figure out how to support FE integration
  • [ ] ability to customise UI labels to match the terms that React users would typically use
  • [ ] smarter reloading/invalidating of view cache

Most helpful comment

For future references: I built my own adapter too (using babel), you can find the source code here https://github.com/guzart/fain/blob/v0.9.0/packages/fain-src/lib/frctl-react-adapter/adapter.js

PS: Thank you for open sourcing fractal.

All 7 comments

I'm just starting to dig in here, I see that the project is on 1.0.8 now.

Is this "1.x" milestone still valid?

got some status on this topic?

+1

so actually i've written my own adapter for react based on: tnottu/fractal-twig-adapter - it's far from perfect but it was not a big challenge to get started with.

For future references: I built my own adapter too (using babel), you can find the source code here https://github.com/guzart/fain/blob/v0.9.0/packages/fain-src/lib/frctl-react-adapter/adapter.js

PS: Thank you for open sourcing fractal.

Be cool to see this as a combined project/adapter as a standalone as an extra to Fractal :)

For those who stumble on this from a Google search like me: There's also an experimental React adapter by Fractal here: https://github.com/frctl/react-adapter

Was this page helpful?
0 / 5 - 0 ratings