-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: appId
argument can be set to Client ID string
#606
Conversation
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labled with |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you also remove
Lines 34 to 38 in 81ac6ec
if (!Number.isFinite(+options.appId)) { | |
throw new Error( | |
"[@octokit/auth-app] appId option must be a number or numeric string", | |
); | |
} |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
5a92718
to
c6189b7
Compare
@@ -152,7 +152,7 @@ export type UTC_TIMESTAMP = string; | |||
export type AppAuthentication = { | |||
type: APP_TYPE; | |||
token: JWT; | |||
appId: number; | |||
appId: number | string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a later date, maybe we could use template literal strings to better define the format
appId: number | string; | |
appId: number | `Iv1.${string}`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, this would imply a change in universal-github-app-jwt
first. Do you want me to open an issue there first?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
appId: number |
Iv1.${string}
;
I wouldn't do that, because there is a chance that future Client IDs will start with lv2....
and I also think there are old apps that still have a client ID without the lv1
prefix
appId
argument can be set to Client ID string
@oscard0m if it's done from your side, can you let me merge it please? I want to test out the latest |
go for it @gr2m |
🎉 This PR is included in version 7.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@oscard0m should I create an issue to update the README? By my reading, the appId is required and clientId is optional, which confused me. I didn't see any mention that clientId could be assigned to appId. |
that would be great, thank you! |
appId
allows string or number as typeResolves #603
Before the change?
appId
only allowednumber
as type.After the change?
appId
allowsnumber
orstring
as type.Pull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!