Ecosyste.ms: Funds
An open API service for providing issue and pull request metadata for open source projects.
https://github.com/go-warnings/warnings
Last synced: about 4 hours ago
Repository metadata:
Package warnings implements error handling with non-fatal errors (warnings).
- Host: GitHub
- URL: https://github.com/go-warnings/warnings
- Owner: go-warnings
- License: bsd-2-clause
- Created: 2016-08-14T17:36:57.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2018-03-27T03:11:48.000Z (over 6 years ago)
- Last Synced: 2024-10-29T19:58:49.278Z (11 days ago)
- Language: Go
- Homepage: https://gopkg.in/warnings.v0
- Size: 4.88 KB
- Stars: 4
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README
- License: LICENSE
Owner metadata:
- Name:
- Login:
- Email:
- Kind:
- Description:
- Website:
- Location:
- Twitter:
- Company:
- Icon url:
- Repositories:
- Last Synced at:
- Profile URL:
- Sponsor URL:
Committers metadata
Last synced: about 7 hours ago
Total Commits: 6
Total Committers: 1
Avg Commits per committer: 6.0
Development Distribution Score (DDS): 0.0
Commits in past year: 0
Committers in past year: 0
Avg Commits per committer in past year: 0.0
Development Distribution Score (DDS) in past year: 0.0
Name | Commits | |
---|---|---|
speter | s****1@g****m | 6 |
Issue and Pull Request metadata
Last synced: about 4 hours ago
Package metadata
- Total packages: 1
- Total downloads: unknown
- Total dependent packages: 0
- Total dependent repositories: 0
- Total versions: 3
go: github.com/go-warnings/warnings
Package warnings implements error handling with non-fatal errors (warnings). A recurring pattern in Go programming is the following: This pattern allows interrupting the flow on any received error. But what if there are errors that should be noted but still not fatal, for which the flow should not be interrupted? Implementing such logic at each if statement would make the code complex and the flow much harder to follow. Package warnings provides the Collector type and a clean and simple pattern for achieving such logic. The Collector takes care of deciding when to break the flow and when to continue, collecting any non-fatal errors (warnings) along the way. The only requirement is that fatal and non-fatal errors can be distinguished programmatically; that is a function such as must be implemented. The following is an example of what the above snippet could look like using the warnings package: For an example of a non-trivial code base using this library, see gopkg.in/gcfg.v1 Rules for using warnings TODO
- Homepage: https://github.com/go-warnings/warnings
- Documentation: https://pkg.go.dev/github.com/go-warnings/warnings#section-documentation
- Licenses: BSD-2-Clause
- Latest release: v0.1.2 (published almost 7 years ago)
- Last Synced: 2024-11-09T00:03:53.361Z (1 day ago)
- Versions: 3
- Dependent Packages: 0
- Dependent Repositories: 0
-
Rankings:
- Dependent packages count: 6.999%
- Forks count: 7.013%
- Average: 7.829%
- Stargazers count: 7.96%
- Dependent repos count: 9.346%