-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Internal assets aren't being found even that they exist #324
Comments
hey Zoey, sorry I hadn't much time lately to work on the storybook, but I'm now tackling all open issues. |
yes, it is! |
Ok, I’ll try to reproduce your error tomorrow! |
Hey Zoey, it took me a couple of hours to dig down to the issue, but the problem was you are not providing the storybook a LiveView endpoint. I fixed it with:
Let me know if it's working for you! |
I'm closing, feel free to re-open if you are still stuck with this issue. |
I have an umbrella app which has many web apps of different domains. However, I would like to extract common components and styles to a separate application called
:design_system
.To correctly forward and handle different paths request I also have a
:proxy_web
app that forwards to the respective endpoint based on theconn.path_info
pattern.Here's the
ProxyWeb
main part, the router:Thats works fine, but
phoenix_storybook
has a strange behaviour.In my
:design_system
app I define the router as:So now I'm able to reach
/design-system/storybook/assets/css/app.css
for example, in the browser!However, when I reach to
/design-system/storybook
the page reloads infinitely because the conn is halted on theAssetNotFoundController
ofphoenix_storybook
The partial log is
Sample Video
Screen.Recording.2023-07-25.at.18.09.02.mov
The complete source code can be found at https://github.com/peapescarte/pescarte-plataforma/tree/feat/design-system-app
The text was updated successfully, but these errors were encountered: