Skip to content
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

Swift Package Manager support #34

Merged
merged 21 commits into from
Oct 15, 2024
Merged

Conversation

Ericarman
Copy link
Contributor

@Ericarman Ericarman commented Oct 14, 2024

Changes

  • Made EventManagerConfig initializer public.
  • Added Swift Package Manager (SPM) support.
  • Removed Podfile
  • Created separate target for framework and example application
  • Renamed target to "Seatsio" to align with Swift Package naming conventions.

Testing

  • Verified the SPM integration in a development project.
  • Executed pod lib lint to validate the CocoaPods configuration.

Podfile Outdated
@@ -1,5 +1,6 @@
platform :ios, '12.0'
Copy link
Contributor

Choose a reason for hiding this comment

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

@mroloux @bverbeken looks like README.md is out of date, it says we support minimum version iOS 9.0 and newer

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@schaloner I have updated README.md

@Ericarman Ericarman requested a review from schaloner October 15, 2024 06:31
Podfile.lock Outdated
@@ -1,3 +1,16 @@
PODFILE CHECKSUM: 7e3d3d38e3c6c64c581bdfbe83e25e0034c3de26
PODS:
Copy link
Member

Choose a reason for hiding this comment

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

I'm far from an expert, but why does Prodfile.lock need a reference to v17 of its own project?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

For the future, it would be good to have separate targets for the app (example) and library (seatsio) and use the library in the app for testing.

I'm using the development pod here to see how the pod will be generated as we use the same target for the library and example app.
https://guides.cocoapods.org/making/development-cocoapods.html

I'll set up multiple targets as soon as I have a bit of free time!

Copy link
Member

Choose a reason for hiding this comment

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

👍

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mroloux , I've separated the example app and framework. Could you please review it once more? Also, could you set up the actions to skip running the pod install?

Copy link
Member

@mroloux mroloux Oct 15, 2024

Choose a reason for hiding this comment

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

Maybe it's better if you remove pod install in this branch? Then we see if the build succeeds.

It's in build.yml and release.yml.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@Ericarman Ericarman requested a review from mroloux October 15, 2024 07:22
@@ -1,5 +0,0 @@
platform :ios, '12.0'

target 'seatsio-ios' do
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Podfile is not needed anymore.

@mroloux mroloux merged commit 8a24f08 into seatsio:master Oct 15, 2024
1 check passed
@Ericarman Ericarman deleted the feature/spm-support branch October 15, 2024 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants