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

feat: Restructure for better support and maintenance #46

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

rynecheow
Copy link
Member

Non-functional changes

  • Restructure directory to be more consistent
  • Moved CircleCI to GitHub Actions to test and release to on Cocoapods and release xcframeworks
    (The above changes were made similar to RxAlamofire & RxRealm)

Breaking changes

  • Supports RxSwift 6.0

@rynecheow rynecheow force-pushed the feat/v2.0.0 branch 2 times, most recently from 19d0223 to 46fd4b8 Compare January 4, 2021 04:11
BREAKING CHANGE:
- Moved circleci to githubci
- Supports RxSwift 6.0
- Release xcframeworks
@mRs-
Copy link
Member

mRs- commented Jan 13, 2021

It seems that the builds are failing. Do you like to fix this as well?

@rynecheow
Copy link
Member Author

Hi, this PR moves the pipeline to GitHub CI - hence the build on Circle will fail. It'll take some work if we were to fix Circle's pipe.

@mRs-
Copy link
Member

mRs- commented Jan 13, 2021

Can you maybe elaborate what the hell did you do here? You moved every inch of the package 😄 (no offense) but what exactly was the motivation about this?

@freak4pc
Copy link
Member

I think Ryne has a bunch of automatons and stuff he uses for his community projects in RxSwiftCommunity, but I agree this is a really gigantic PR which makes it hard to review.

@rynecheow I'm wondering if there's any way to break these changes into smaller consumable PRs (For example, adding Danger and Swiftformat, other changes), or must everything go in a single one ?

@rynecheow
Copy link
Member Author

@mRs- Am first of all sorry about the gigantic PR! Every change is kinda tied to one another but yes, I can help to break this up into smaller commits, if we need to break up the PR, but unravelling the changes might take me some time, and I hope I can find some time to do that over the next month.

What I can probably do is break into several commits from the same change, in the same PR, so that it is clearer what was done, and also change Circle's CI file to at least pass the current change and remove it later.

@mRs-
Copy link
Member

mRs- commented Jan 21, 2021

I'm going through it next week to get this done as fast as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants