*** Skipped building Then due to the error: Dependency "Then" has no shared framework schemes

Please follow this guide to fix -> https://github.com/Carthage/Carthage#share-your-xcode-schemes

lazy var tableView: UITableView = { let tabView =UITableView.init(frame: .zero, style: .plain) tabView.backgroundColor = UIColor.white tabView.dataSource = self tabView.delegate = self return tabView }() I often use lazy loading， and，how to write by Then。Can you give me a test code。

Hey!

I really like then approach and wanted to extend it for optionals. Feature implemented in this PR is different from current Then, however similar in ideology.

It allows calling any custom block of code on optional, if optional contains .Some. Most common case for this would be [weak self] in various kinds of completion blocks, however there are a lot more cases where you can use this approach.

For example, let's say we need to use weak self, however pass self somewhere else as unwrapped optional, like this:

self.doSomethingWithCompletion { [weak self] result in
    self?.parseResult(result, receivedFrom: self!)
    self?.doSomething()
}

This would require multiple optional unwrappings and possibly even force unwraps. Another way to do this is to unwrap with guard:

self.doSomethingWithCompletion { [weak self] result in
    guard let strongSelf = self else { return }
    strongSelf.parseResult(result, receivedFrom: strongSelf)
    strongSelf.doSomething()
}

Unwraps are gone, however we introduced new variable for self, which is not really convenient. Meet Then from this PR:

self.doSomethingWithCompletion { [weak self] result in
    self.then {
        $0.parseResult(result, receivedFrom: $0)
        $0.doSomething()
    }
}

I propose we add one more function - when. This serves exactly the same purpose, but "then" is only executed when initial condition is met. This is extremely useful in a lot of cases, as it changes often used syntax

if (true) {
    label.then {
        ...
    }
}

to

label.when(true) {
    ...
}

The only problem is that it does not fit with name of your repository :D but I think it is okay :)

ERROR ITMS-90056: "This bundle Payload/X.app/Frameworks/Then.framework is invalid. The Info.plist file is missing the required key: CFBundleVersion."

Instead of creating a new instance for a view, is there a possibility to fetch the existing instance and set attributes to it? I want to update attributes initially for IBOutlets views.

when I use it with cocoapods ,I will get the issues "Command /bin/sh failed with exit code 1", but not appear other what like "then".it is my pods file:

platform :ios, '9.0' use_frameworks!

target 'MapInSwift' do pod 'Alamofire' pod 'SwiftyJSON' pod 'Then', '~> 2.1' end

if i remove the line with "pod 'Then', '~> 2.1'", i will get no issue

I fand the solution on the google but no way is fit me.If i need particular setting with Xcode(xcode 8.0; swift 3.0)

I can't seem to access class variables in my then block:

For example

class GradientView {
   let colors = ...
   lazy var gradientLayer = CAGradientLayer().then {
       $0.colors = self.colors // also tried colors
   }
}

doesn't work, but

class GradientView {
   let colors = ...
   lazy var gradientLayer: CAGradientLayer = {
       let layer = CAGradientLayer()
       layer.colors = self.colors
       return layer
   }()
}

does.

Can I repeat my old pattern of accessing instance variables in a lazy init using Then?

Problem

The code below works in Then 1.0.1 but doesn't work in 1.0.2.

func tempt(label: UILabel) {
    label.text = "I💞Then"
}

let label1 = UILabel()
tempt(label1) // Works fine definitely
UILabel().then(tempt) // Error: Cannot convert value of type '(UILabel) -> ()' to expected argument type 'inout UILabel -> Void'

Adding inout keyword to the func resolves the error, but it brings another problem.

func temptInOut(inout label: UILabel) {
    label.text = "I💞Then"
}

UILabel().then(temptInOut) // Works fine

let label2 = UILabel()
temptInOut(label2) // Error: Cannot convert value of type 'UILabel' to expected argument type 'inout UILabel'
temptInOut(&label2) // Another Error: Cannot pass immutable value as inout argument: 'label2' is a 'let' constant

To resolve all errors, I should write code as below.

var label3 = UILabel()
temptInOut(&label3) // Works fine but seems ugly.

I don't use neither var nor &...

Proposal

#18 is nice-to-have modification, but old-style method(without inout keyword) is also nice in some situations.

So why don't you implement another old-type method as (@noescape block: Self -> Void) -> Self ?

I got compiling error Cannot convert value of type '_ -> ()' to expected argument type 'inout WKWebView -> Void' with this code

webView.then {
    $0.navigationDelegate = self
}

However, the error's gone when there are two assignments in the block

webView.then {
    $0.navigationDelegate = self
    $0.tag = 1
}

I'm using this library in a Vapor project which needs to run on Linux and I found that Then won't build on Linux because CoreGraphics isn't available so I've wrapped all CoreGraphics import and all the CG* extensions in #if !os(Linux) checks.

Motivation

To mutate some deeply nested value types, we have to write the whole key path at least twice:

some.very[deep].structure.someProperty = someValue
some.very[deep].structure.anotherProperty = anotherValue

// or with Then:

some.very[deep].structure = some.very[deep].structure.with {
    $0.someProperty = someValue
    $0.anotherProperty = anotherValue
}

Solution

Let's extend Then with mutate function (alternatives: update, access, write):

extension Then {
    public mutating func mutate(_ block: (inout Self) throws -> Void) rethrows {
        try block(&self)
    }
}

Usage:

some.very[deep].structure.mutate {
    $0.someProperty = someValue
    $0.anotherProperty = anotherValue
}

It would be great to have this in Then library. Thank you!

Has Then been abandoned?  It doesn't appear @devxoul has responded to any issues or PRs, or made any code changes since Sept 2019.  And basically every comment he made before than was highly resistant to making any changes or accommodations for the devs who rely on Then.

Is it time for someone else to take over the project?  Is there someone else who is already maintaining an updated fork who's willing to take up the mantle of maintaining the community, and who welcomes us all switching over to his/her fork?

Side-note: I grew tired of some of the issues with Then a while back and wrote my own stab from scratch at solving this problem— I chose to go with a free function approach that's closer to the with keyword in Python, JavaScript, Visual Basic, Object Pascal, Delphi and using in C#, and which seems to be more idiomatic Swift.  I also care about making sure my libraries work in every build toolchain and environment (SPM, CocoaPods, Carthage, Xcode project embedding, etc.); can solve any reasonable user-requested problem (@discardableResult, arbitrary return value, @inlinable, etc.); and can be used freely by everyone (completely copyright-free public domain, no restrictions or attribution needed).  My recently-uploaded library is called With.

The .gitignore file currently is ignoring xcodepoj-related files, which currently does nothing for the Then project because of the decision to go full SPM and remove all xcodeproj stuff (#55).

However, ignoring these files causes issues when Then's source is included in outer Git repo (via git-subtree or direct copying of project) such as when using Carthage or manual library management in conjunction with a generated xcodeproj (swift package generate-xcodeproj). Because Then's .gitignore is picked up by the enclosing repo, that prevents the generated xcodeproj or shared schemes from being able to be checked-in— which should arguably be under the discretion of the enclosing repo's build setup.  Removed the ignores for xcodeproj and xcshareddata to fix this, and removed the xcuserdata line too for good measure (again, if there's no xcodeproj in Then, there's no need to ignore it).