-
Notifications
You must be signed in to change notification settings - Fork 78
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
Should characterize be kicked off by Sufia::GenericFile::Actions.create_content? #232
Comments
Not having my head in the code lately, I ask what may be an obvious question: can we rely upon |
@mjgiarlo Aye, the huge advantage is that we know it works. Another drawbacks is that it is slowing down our system considerably, because it's always checks for content change on every save. We can shoulder some of that responsibility as coders by agreeing that we always deposit files via the Sufia::GenericFile::Actions.create_content service method. |
Instead run the characterization from the FilesControllerBehavior. This makes testing far easier. Fixes #232
Instead run the characterization from the FilesControllerBehavior. This makes testing far easier. Fixes #232
Instead run the characterization from the FilesControllerBehavior. This makes testing far easier. Fixes #232
This makes testing far easier. Fixes #232
This makes testing far easier. Fixes #232
This makes testing far easier. Fixes #232
This makes testing far easier. Fixes #232
Then we can remove the
around_save :characterize_if_changed
from GenericFile.This makes the code easier to follow.
The text was updated successfully, but these errors were encountered: