Skip to content
This repository was archived by the owner on Sep 6, 2021. It is now read-only.

Conversation

@dangoor
Copy link
Contributor

@dangoor dangoor commented Mar 27, 2013

With this change, we can use npm pack to create a package that we can install into the brackets-registry project as a simple way to share this bit of code.

dangoor added 4 commits March 26, 2013 16:26
The validation code is no longer in ExtensionManagerDomain itself.
For the extension registry, we want package.json to be required.
With this change, the validation code allows optional checking for package.json.
@ghost ghost assigned njx Mar 27, 2013
@njx
Copy link

njx commented Mar 27, 2013

Reviewing.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should include a files attribute that only includes the files we intend to share with the registry server. The answer is probably "no"...but was just wondering what you were thinking about it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I was thinking it's not worth bothering with. Maybe if we start having a lot more code that is Brackets-client specific.

@njx
Copy link

njx commented Mar 27, 2013

Merging--the comments were just for minor information and can be addressed later.

njx pushed a commit that referenced this pull request Mar 27, 2013
Breaks out package validation for sharing with brackets-registry
@njx njx merged commit b99fe36 into master Mar 27, 2013
@njx njx deleted the dangoor/shared-extensibility branch March 27, 2013 16:23
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants