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

test: [DO NOT MERGE] Run ParseUI Swift Demo without Dynamic Targets #1757

Closed
wants to merge 2 commits into from

Conversation

dplewis
Copy link
Member

@dplewis dplewis commented Oct 7, 2023

New Pull Request Checklist

Issue Description

The only way to remove Bolts from Carthage is to remove all Dynamic Targets. ParseUI Swift Demo is the only target using it. I'm wondering why its not included in the CI build. If this test fails then we will have to remove the ParseUI swift support from the Repo unless we want to keep Bolts Carthage.

Looks like Bolts Carthage has already started failing in other Jobs

https://github.com/parse-community/Parse-SDK-iOS-OSX/actions/runs/6441796016/job/17491943259?pr=1756
https://github.com/parse-community/Parse-SDK-iOS-OSX/actions/runs/6440880523/job/17490133303

@parse-github-assistant
Copy link

parse-github-assistant bot commented Oct 7, 2023

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

@dplewis dplewis changed the title [DO NOT MERGE] Run ParseUI Swift Demo without Dynamic Targets test: [DO NOT MERGE] Run ParseUI Swift Demo without Dynamic Targets Oct 7, 2023
@dplewis dplewis requested a review from a team October 7, 2023 15:19
@dplewis
Copy link
Member Author

dplewis commented Oct 7, 2023

@mtrezza Looks like Bolts Carthage is broken. I can't run this test.

@dplewis dplewis closed this Oct 7, 2023
@dplewis dplewis reopened this Oct 7, 2023
@mtrezza
Copy link
Member

mtrezza commented Oct 7, 2023

Then should we remove the ParseUI?

@dplewis dplewis closed this Oct 8, 2023
@dplewis dplewis deleted the swiftuidemo branch October 8, 2023 12:50
@dplewis dplewis restored the swiftuidemo branch October 8, 2023 12:51
@dplewis dplewis reopened this Oct 8, 2023
@dplewis
Copy link
Member Author

dplewis commented Oct 8, 2023

Then should we remove the ParseUI?

Yes please! Users should be making their own UI

@mtrezza
Copy link
Member

mtrezza commented Oct 8, 2023

I agree, this to me seem like it used to be a convenience feature back in the days, but today - especially with SwiftUI - building a layout has become a lot easier. I believe we can remove that.

@dplewis
Copy link
Member Author

dplewis commented Oct 8, 2023

@mtrezza Can you open an issue?

@mtrezza
Copy link
Member

mtrezza commented Oct 8, 2023

See #1760

@dplewis dplewis closed this Oct 12, 2023
@dplewis dplewis reopened this Oct 12, 2023
@dplewis
Copy link
Member Author

dplewis commented Oct 13, 2023

Closing via #1763

@dplewis dplewis closed this Oct 13, 2023
@dplewis dplewis deleted the swiftuidemo branch October 13, 2023 06:35
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.

2 participants