To be able to consume sentry-conventions as a Swift Package Manager dependency, we need to create a a standard Swift package.
This includes:
Package.swift in the repository root
- Source code can be in custom nested path
- Tagged commits is enough to define releases
Ideas to brainstorm and discuss:
- We should consider using strongly-typed enums over static constants, if it has a benefits
- We need to decide if we build it on-top of external tooling such as SwiftGen or if we want to build custom scripts
References:
To be able to consume sentry-conventions as a Swift Package Manager dependency, we need to create a a standard Swift package.
This includes:
Package.swiftin the repository rootIdeas to brainstorm and discuss:
References: