-
Notifications
You must be signed in to change notification settings - Fork 156
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
Support apps/plugins #2
Comments
The server must have authority about what frontend components/apps can be loaded for the current user. This means the frontend apps don't need to know about each other directly. |
This also means that the frontend alone doesn't know anything about installed modules. The frontend brings in some modules in different paths as webpack bundle (one bundle per app/module) and the main page needs to query the server to find out what modules to load. At development time we could provide a static JSON file on the dev server to be able to load modules for when no backend is available at all. |
I am still working on an easy way to use vue.js's component system to serve extension points in phoenix. An API needs to tell phx what to load simply by populating an object little data. Jet there still is the need to deploy frontend code and other assets on the frontend-server as well as backend-code to the core-server. |
@felixheidecke please link with tickets / PR related to app loading |
implemented |
We need a clearly defined mechanisms to allow frontend apps to properly hook into phoenix.
At best we allow to reuse existing web front ends like built in the contacts app as example.
Please make sure the #1 applies in here as well.
The text was updated successfully, but these errors were encountered: