Verbose mode on the plugin?

[marcosboger]

As mentioned in #1060, we are running the plugin using this trick to deploy in ANT/MDAPI format. It would be really helpful if there was a verbose mode on the plugin for ex showing the git diff, what files it's including in the package.xml and why.

[scolladon]

Hi !

I'll implement a logger soon, so we can have more information about what is happening.
I just need some time to design the way it should be used

[scolladon]

That's very nice of you !
I'll try to write something done and share that so you can contribute :)

[marcosboger]

@scolladon could I try and implement something regarding this? 🙂
Do you already have any logging framework or library in mind?

My thinking is to create more "traceability" for the plugin. In verbose mode, we would add logs (either to a file or stdout directly) explaining what was analyzed and included (or not) in package.xml

Example:

[INFO] ApexClassName__c.cls file contains changes (+13 additions, -7 deletions). It will be included in package.xml
[WARN] Admin.profile-meta.xml file contains only deletions (-10 deletions). It will NOT be included in package.xml. (link to docs explaining why, if we have)
[INFO] CustomerManager.profile-meta.xml contains changes (+1 addition, -1 deletion). It will be included in package.xml

What do you think? This could increase greatly our understanding of the plugin's behavior and help in troubleshooting.

[scolladon]

Yes I really like this logging feature
I started to play with the SF CLI logger to have a more native handling for the end user
I think I have something easy to implement / test / use (native SF CLI logger)

I'll try to ship something soon, if you want you can help QA this (User Experience, etc)

[marcosboger]

Yeah, I'm down for QAing the feature 👍 Just let me know when help is needed.

Also, if help needed implementing, I'm also up to it 😉

[scolladon]

I just created a draft PR @marcosboger (#1123)
For now there is just the logger service
I'll start implementing logs into it soon
You'll be able to test and share your opinion about what should be logged, how and where in the code :)