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
Parentwork plugin copious output during import #4120
Comments
FWIW, this seems to match the behavior of mbsync, at least when running after import. |
Yes, I wanted to match the behaviour of mbsync, but I don't want it to run on import. I will check the other plugins on how they display changes only when they specifically are called and not via an event. |
This is still an issue, making the Parentwork plugin almost useless as it prints right over the base Lines 205 to 211 in b116eb5
completion_script(commands) function: Lines 1813 to 1817 in b116eb5
|
For now, until I have more time to dig into the code, I simply removed lines 207:211 in my local plugin file. |
I wrote up a quick change to only output verbose details when running explicitly. Let me know if there's anything I should change with that. |
When the parentwork plugin is enabled during import, it outputs its changes all over the rest of the import UI, like so:
This makes it hard to know what to input if I take too long and the parentwork outputs a lot of text. This should probably be silenced during import (when there is nothing that it's changing from anyways.
The output (I'm fairly sure) is from
ui.show_model_changes
, but I'm not sure if that should be changed to not output during import or for parentwork to not call it during an import.The text was updated successfully, but these errors were encountered: