-
Notifications
You must be signed in to change notification settings - Fork 85
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: [#49] Support Package Development #159
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #159 +/- ##
==========================================
+ Coverage 52.10% 52.46% +0.35%
==========================================
Files 117 118 +1
Lines 8097 8326 +229
==========================================
+ Hits 4219 4368 +149
- Misses 3565 3647 +82
+ Partials 313 311 -2
☔ View full report in Codecov by Sentry. |
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.
The master branch has an error now, the error is fixed in this PR and the PR needs the function in this file, so I optimized the console module here.
&command.BoolFlag{ | ||
Name: "existing", | ||
Aliases: []string{"e"}, | ||
Usage: "Publish and overwrite only the files that have already been published", | ||
}, | ||
&command.BoolFlag{ | ||
Name: "force", | ||
Aliases: []string{"f"}, | ||
Usage: "Overwrite any existing files", | ||
}, | ||
&command.StringFlag{ | ||
Name: "package", | ||
Aliases: []string{"p"}, | ||
Usage: "Package name to publish", | ||
}, | ||
&command.StringFlag{ | ||
Name: "tag", | ||
Aliases: []string{"t"}, | ||
Usage: "One tag that have assets you want to publish", | ||
}, |
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.
We can use different types of flags after optimizing the console module above.
return paths | ||
} | ||
|
||
func (receiver *VendorPublishCommand) packageDir(packageName string) (string, error) { |
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.
We can get the file content in a third package by go/build
package, then we can publish the content to project.
There is an example PR of how to build a third package: goravel/goravel#147
Close: goravel/goravel#49