tidybyt/community GitHub Workflow check for print statements about community HOT 6 CLOSED

I don't think having some print statements present is necessarily a bad thing. But if you have tons you could create a debug variable and set to false in the community app and change in production worst case if you don't want to just comment them out.

from community.

or (and I don't know if this is possible) - shunt that output during compile/test in the workflow so it doesn't flood the github logs.

from community.

So I'm sure it is possible, but even if it doesn't flood the github logs, I think it would still flood their logs on their servers?

I was simply giving you an alternative if you wanted at least a quicker temporary fix if this is possible to do. Not having to worry about commenting them out would be nice though, I don't disagree.

from community.

I don't typically leave them in code I submit - I use it for debugging & then delete them. But I see other folks still have them. was helping someone else out with a failed test & I had to weed through a bunch of another submitter's app debugging/print to find the error in the app we were working on. Just trying to streamline it as a general rule. we're on the same page.

from community.

Yeah, I'm with you if they are super useful and beyond just hit or miss on the api, usually they get commented out or just deleted.

But agreed, wading through those is a pita.

from community.

We're automatically closing this issue because it hasn't had any activity in 30 days. If that seems like a mistake, please feel free to re-open. Thanks!

from community.