-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
chore: remove watcher polling option #7480
Conversation
Deploying with Cloudflare Pages
|
We should maybe include a migration to delete the option from the database |
Totally forgot about that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Seeing such a diff always makes me happy :)
If most people won't use it anyways I think removing this makes sense.
Is there an easy way to create a migration for a config change? Typeorm doesn't see any changes |
This is a breaking chance because we removed a feature. There is no breaking changes on database level or deployment method, correct? |
There are no schema changes, you just need to write a migration that will delete the key if it has been set. Take a look at:
You can generate an empty migration with |
Yes, we are removing an fature that was previously available but mostly seems to be causing problems. Those who wish to use a polling-type library refresh should use the cron feature instead. The library watcher is still available for those who don't mount their external libraries from a network drive. |
Can you link to the issue(s) where these problems were detailed? |
Polling for the library watcher only seems to bring problems. If users want to rescan libraries automatically we should probably have them use the cron feature instead.