Skip to content

Jetstream components #1269

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

Closed
amihailov opened this issue Feb 21, 2023 · 2 comments
Closed

Jetstream components #1269

amihailov opened this issue Feb 21, 2023 · 2 comments

Comments

@amihailov
Copy link

amihailov commented Feb 21, 2023

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.

@timacdonald
Copy link
Member

Jetstream is only meant to be installed in new applications. See the installation documentation.

Screen Shot 2023-02-22 at 9 06 46 am

@amihailov
Copy link
Author

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants