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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swift 4.2 #883

Merged
merged 4 commits into from Sep 30, 2018
Merged

Swift 4.2 #883

merged 4 commits into from Sep 30, 2018

Conversation

nathantannar4
Copy link
Member

What does this implement/fix? Explain your changes.

Updates the codebase to Swift 4.2, specifies Swift 4.2 version of MessageInputBar, update CircleCi config

Does this close any currently open issues?

Everyone requesting Swift 4.2 馃槉

Any other comments?

Sorry to those who have submitted Swift 4.2 PRs already. #880 was branched from master, not development and we have already made changes in development

For those who want early access, use the branch swift-4.2

This will segue MessageKit to its 1.1 release

@nathantannar4 nathantannar4 added this to the 1.1 milestone Sep 29, 2018
@nathantannar4 nathantannar4 self-assigned this Sep 29, 2018
@nathantannar4 nathantannar4 changed the base branch from master to development September 29, 2018 18:51
Copy link
Member

@SD10 SD10 left a comment

Choose a reason for hiding this comment

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

@nathantannar4 Please add a CHANGELOG entry for the upcoming release - "Added Swift 4.2 support"

@SD10 SD10 mentioned this pull request Sep 29, 2018
@@ -28,7 +28,7 @@ open class PlayButtonView: UIView {

// MARK: - Properties

open let triangleView = UIView()
public let triangleView = UIView()
Copy link
Member

Choose a reason for hiding this comment

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

Emm, how about make it open and var?

Copy link
Member Author

Choose a reason for hiding this comment

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

What would be the use case for allowing someone to set a new value?

Copy link
Member

Choose a reason for hiding this comment

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

Maybe users want to do some custom things? Make it open have no side-effect, right?

Copy link
Member Author

Choose a reason for hiding this comment

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

Before it was open but a let. So technically they can't change it. But if it's changed to var someone can set it to something. But if they set it that won't automatically add the new view to the superview or lay it out.

@nathantannar4 nathantannar4 merged commit 095abe0 into development Sep 30, 2018
@hyouuu
Copy link
Contributor

hyouuu commented Oct 1, 2018

This is awesome! Please update MessageInputBar as well :D

@hyouuu
Copy link
Contributor

hyouuu commented Oct 1, 2018

Oh I see the repo is updated, but cocoapod didn't update it - probably because the podspec didn't specify a version. I had to add MessageInputBar directly in my pod file, then it was updated from 0.2.2 to 0.4.0

@talanov
Copy link
Contributor

talanov commented Oct 1, 2018

@nathantannar4 PodSpec invalid, MessageKit's InputBar automatically install 0.2.2 version instead of 0.4.

@nathantannar4
Copy link
Member Author

nathantannar4 commented Oct 1, 2018

@talanov I didn't officially released a new pod version for MessageInputBar bar since this is wasn't a release yet. You will need to specify the version until official release.

Sent with GitHawk

@SD10
Copy link
Member

SD10 commented Oct 1, 2018

@nathantannar4 You can release MessageInputBar 0.4.0 though? It shouldn't be blocked by a MessageKit release

@SD10 SD10 deleted the swift-4.2 branch October 1, 2018 20:38
@nathantannar4
Copy link
Member Author

Sure, released just now

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.

None yet

5 participants