You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently working on several projects that make extensive use of engines to break large code bases into manageable chunks, and with the current react_on_rails configuration setup, it is very difficult to work with client code from several engines independently.
I'm working on a fork that will allow a per-engine configuration process for the ReactOnRails gem in such a way that including engines with ReactOnRails UIs simply works at the main application level.
I would love to discuss possible pitfalls and challenges you see with this approach.
The text was updated successfully, but these errors were encountered:
I am currently working on several projects that make extensive use of engines to break large code bases into manageable chunks, and with the current react_on_rails configuration setup, it is very difficult to work with client code from several engines independently.
I'm working on a fork that will allow a per-engine configuration process for the ReactOnRails gem in such a way that including engines with ReactOnRails UIs simply works at the main application level.
I would love to discuss possible pitfalls and challenges you see with this approach.
The text was updated successfully, but these errors were encountered: