Improve support for Swift language

1. Some Swift language entities and properties are missing

• Swift entities are the following: class, struct, protocol, enum

• Swift properties can be: var, let

• Missing implementation: protocol, enum, let

1. Swift Entities dependencies are not evaluated when used as static

example:

class A {
 static let shared = A()
 
 func doSomething() {
  print("A")
 }
}

class B {
 func doSomethingWithA() {
  A.shared.doSomething()
 }
}

The class B depends from A, but the relation is not implemented in the output.

Proposed output

Consider the following valid swift example:

protocol Naming {
    var name: String { get set }
}

protocol Describing {
    var describing: String { get }
}

class ClassA: Naming & Describing {
    
    static let shared = ClassA()
    
    var name: String = "A"
    let id: UUID = UUID()
    var describing: String = "Class A"
}

class ClassB: ClassA {
    func show() {
        print(name)
    }
}

enum EnumA {
    case one
    case two(EnumB)
}

enum EnumB: String, Describing {
    case one
    case two
    
    var describing: String {
        self.rawValue
    }
}

struct StructC<T: Naming>: Describing {
    var name: String = "C"
    let state: EnumA = .one
    var generic: T
    
    var describing: String = "Class C"
    
    init(generic: T) {
        self.generic = generic
    }
}

public struct EmergeSwiftTest {
    public private(set) var text = "Hello, World!"

    var b = ClassB()
    let eB: EnumB = .one
    let eA = EnumA.two(.one)
    
    func show() {
        b.show()
        print(ClassA.shared.name)
    }
}

actual output:

desired output:

• Naming doesn’t depend from other entities
• Describing doesn’t depend from other entities
• ClassA depends on Naming, Describing
• ClassB depends on ClassA
• EnumA depends on EnumB
• EnumB depends on Describing
• StructC depends on Naming, Describing, EnumA
• EmergeSwiftTest depends on ClassB, EnumB, EnumA, ClassA

note:

• String and UUID are ignored in this context as they should appear as dependency on the Foundation framework

I’ve prepared a version solving the point 1. Happy to do a PR if you are interested. Not sure how to sort out point 2 though.

[glato]

@Andrea-Scuderi I’ve merged your PR #13, will try to follow up on an approach for point 2 in a couple of days.

[glato]

Hi @Andrea-Scuderi 👋, thank you for the interesting ideas and enhancements, I’d appreciate any contribution and help. If you’ve already prepared a PR to solve point 1, I’d be happy to review/test/merge your solution. I’ll try to come up with an approach for point 2 in the following days.