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
This PR #1118 changed the way Jetstream components are handled.
They are now copied under generic names in the view components folder.
If one installs Jetstream on an existing project it overwirtes any existing components in the project having the same name whitout any warning (same for overwriting the existing User Model or the layout files).
Basically this makes Jetstream usable only on brand new projects, otherwise it could be havoc.
Since Jetstream components / resources are package specific, they should live in their own space.
The text was updated successfully, but these errors were encountered:
I know that, I've read the docs. I have used Jetstream since a while. And still, (over)writing so many generic name components in the user basic components folder whitout any prompt is wrong at some many levels...
This PR #1118 changed the way Jetstream components are handled.
They are now copied under generic names in the view components folder.
If one installs Jetstream on an existing project it overwirtes any existing components in the project having the same name whitout any warning (same for overwriting the existing User Model or the layout files).
Basically this makes Jetstream usable only on brand new projects, otherwise it could be havoc.
Since Jetstream components / resources are package specific, they should live in their own space.
The text was updated successfully, but these errors were encountered: