Shift
eris
Shift | eris | |
---|---|---|
2 | 3 | |
55 | 1,399 | |
- | 0.0% | |
5.5 | 0.0 | |
6 months ago | about 1 year ago | |
Swift | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Shift
-
Looking for EventKit Tutorials
It also might be worth checking out Shift this seems to be some sort of EventKit wrapper for SwiftUI from UIKit. Another really useful way is Github, honestly looking at how other people are also tackling the problem can be such a good way to improve your code quality and also find quicker solutions. For example: MeetingSwiftUI (credit: shrtlist) - this could be a good base, look at how this user has gone about EventKit, 9/10 it won't answer directly what you are looking for but it sometimes can be the inspiration (and give you the know how) to get you across that line and develop it yourself. Be nice though, if you find it useful give it a star ;)
-
Is there any good documentation on EventKit?
I based my own usage on this lib to suit my needs https://github.com/vinhnx/Shift
eris
-
Will go ever get C/Java style exceptions?
What really sucks IMO is that there's no compiler support for exhaustive error checks, the amount of boilerplate for handling errors, no sum types like Rust, horrible stacktraces unless you use something like eris, the ease with which you can ignore errors, all make for really poor error handling as it remains. It is now the #1 challenge that devs report for Go as per their own survey. We might see some improvements on this front at some point and seeing the new errors.Join stuff is giving me hope
-
Thirteen Years of Go - The Go Programming Language
Attaching stacktraces to errors is one way to make errors more readable. Go has notoriously unreadable errors and when you log the error, the logging function is now at the top of the stack rather than where the error actually originated. There needs to be a simple function that adds some default wrapping when you return an error because as it is, you need packages like Eris to make the errors even halfway readable
-
Zap logging package
Actually just stumbled over eris which seems decent.
What are some alternatives?
errlog - Reduce debugging time. Use static & stack-trace analysis to identify the error immediately.
tracerr - Golang errors with stack trace and source fragments.
StatefulTabView - A SwiftUI TabView that retains the state of each tab as well as some other goodies.
emperror - The Emperor takes care of all errors personally
Xcode-Guide - Xcode Guide.
AsyncObjects - Several synchronization primitives and task synchronization mechanisms introduced to aid in modern swift concurrency.
🎚Shift - 🎚Shift is an optioned circuit breaker implementation
MeetingsSwiftUI - SwiftUI demo project which integrates EventKit and Contacts
Falcon - A Simple Yet Highly Powerful Package For Error Handling
iOS-SwiftUI-Firebase-Login-Template - iOS project boilerplate that handles authentication with Email/Password, Sign in with Google, and Sign in with Apple using Google Firebase.
go-ez - An experimental Go package that allows you to write less error handling and makes the logic look simpler and clearer.