Improved logging capability #3
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added a TODO for where to proceed next co-authored-by: beldougie <[email protected]>
co-authored-by: beldougie <[email protected]>
co-authored-by: beldougie <[email protected]>
co-authored-by: beldougie <[email protected]>
|
Before deleting this branch:
|
More safely handle the attempts tracking
Update transport.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of calling
console.logto log attempts, we have leveraged the JSForce logger.We have also update the JSForce logger to output JSON strings rather than plain message.
The reason for doing these changes is because the
console.loginterferes with the process flow within application such asinvoicerizerandrevenue-and-expense-recongitionwhich usestdout/stdinas transport mechanism between scripts and expecting JSON inputs.