-
Notifications
You must be signed in to change notification settings - Fork 210
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
Allow packaging extension without a publisher #1040
Conversation
src/package.ts
Outdated
|
||
// allow users to package an extension without a publisher for testing reasons | ||
if (manifest.publisher) { | ||
validatePublisher(manifest.publisher); | ||
} |
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.
Something seems off with the types here? If manifest.publisher
does not have | undefined
it should, if it does then validatePublisher
should support validating an undefined publisher?
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.
You are totally right, it's weird because we have different requirements for packaging and publishing but the types are only ensured for publishing currently. I'll create different types and validation for both requirement cases, possibly more debt work to come...
This pull request includes changes to the validation of the publisher field in the package manifest. Previously, the validation was triggered even if no publisher was set. With this change, the validation is only performed if a publisher is specified, allowing users to package an extension without a publisher for testing purposes.
fixes #1029