feat: options.id can be set to Client ID
#98
Merged
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.
This pull request updates the handling and documentation of the
idargument to accept both a number (App ID) or a string (Client ID), enhancing flexibility in accordance with GitHub's recommendations.index.d.tsandinternals.d.tsto allow theidparameter andappIdresult to be either a number or a string.README.mdto clarify thatoptions.idcan be set to either the App ID or Client ID, and recommends using the Client ID forgit.colasdn.topand GHES 3.14+. The resultingappIdcan also be a string accordingly.index.test-d.tsandtest/node.test.jsto verify functionality whenidis set to a string.For more details, open the Copilot Workspace session.