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.

Sign up for GitHub

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

Jump to bottom

suitecrm: Make logging something useful to end-users as well as developers #80

Open

jonathanmaw opened this issue Mar 31, 2023 · 1 comment

Labels

Contributor

jonathanmaw commented Mar 31, 2023 •

edited

Loading

i.e., debugging is useful for:

Capturing what HTTP requests were just sent/received
Capturing what the user model looks like in the source, and target before we start modifying them
Capturing what ModelDifference is generated

Warnings are useful for:

Indicating when something might be going wrong to the end-user

Info is useful for:

Knowing what Lifecycle is currently doing while sitting and watching it run (or looking at logs of what it did later), e.g.
- Fetching users from the source
- Fetching users from the target
- Adding/syncing/removing a particular user

jonathanmaw added the enhancement label

Contributor

thinkl33t commented Dec 5, 2023

Strong agree here - currently when not running in debug mode the output is a blank screen and a flashing cursor for ~10 minutes.

thinkl33t mentioned this issue

target_suitecrm: add functionality to disable accounts instead of delete #108

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment