fix: replace escaped newlines with actual newlines in privateKey values #96
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.
Implements automatic newline conversion for private keys and updates documentation accordingly.
index.js
to automatically replace escaped newlines (\\n
) in theprivateKey
argument with actual newline characters before passing it to thegetToken()
function. This ensures compatibility with private keys defined in environment variables or other sources where newlines are escaped.README.md
file by adding a note under theoptions.privateKey
section. It now informs users that escaped newlines in the private key will be automatically replaced with actual newline characters, accommodating private keys stored with escaped newlines.For more details, open the Copilot Workspace session.