Congrats on a super neat project! I wish only that it had a better name.

Ableist language is any word or phrase that intentionally or inadvertently targets an individual with a disability... Examples of ableist language include “crazy,” “insane,” “lame,” “dumb,” “retarded,” “blind,” “deaf,” “idiot,” “imbecile,” “invalid (noun),” “maniac,” “nuts,” “psycho,” “spaz.”

Each of these words, when used flippantly, can be extremely insulting to individuals who find themselves with physical (“lame,” “invalid,” “dumb”) or mental (“crazy,” “retarded,” “psycho”) disabilities.

(via here)

Naming is a Hard Problem™ and I'm guilty of using this language too. I encourage you to consider a new name while this project is still new. Thanks!

Edit: From your own Code of Conduct:

Examples of behavior that contributes to creating a positive environment include:

Using welcoming and inclusive language ... Showing empathy towards other community members

It would be nice to have Sourcery in Homebrew.

Since it's part of the dev tooling, and not the build itself (arguably), I'd prefer not to use CocoaPods for this, but would still be nice to have easy updates with a dependency manager.

Hi, when i tried to build my project with new xcode 11.4 I had this issue with no error description.

Using configuration file at '.sourcery.platform.yml'
Scanning sources...
	loadOrParse: 0.8185429573059082
	resolution took 0.1482919454574585
	combiningTypes: 0.16124391555786133
	total: 0.9820070266723633
Found 213 types.
Loading templates...
Loaded 6 templates.
	Loading took 0.008983016014099121
Generating code...
error: 

If a type inherits from another type, or implements given protocol, should the variables be available in the given type itself? e.g.

protocol Something {
  var typeName: String { get }
}

struct Foo: Something {
}

1. Should we list typeName in Foo? if so should we add alternative variable so people can choose between inherited or direct variables?

2. Also same question can be asked in regards to annotations, if the protocol specified type level annotation, should we flatten that into Foo ?

@ilyapuchka what do you think?

Hi, here at Bending Spoons we decided to leverage Sourcery as a way to generate some code for our applications.

To integrate, in the best possible way, Sourcery with our tooling we would like to embed it in our internal swift CLI.

We are in the process of understanding what is the best way to do so before start coding. We think that the best way would be to have Sourcery as a framework, similarly to Carthage and Swiftlint. Both those projects have a CLI and a Kit and all the functionalities are exposed through API.

What do you think about this approach? Is it something that you would considering doing? Do you suggest a different way to approach this problem? Cheers

cc @lucaquerella

Steps to reproduce:

$ brew install sourcery
$ sourcery --version
1.3.0
$ git clone http://github.com/realm/SwiftLint
$ cd SwiftLint
$ git checkout 92061e8
$ rm Source/SwiftLintFramework/Models/PrimaryRuleList.swift Tests/SwiftLintFrameworkTests/AutomaticRuleTests.generated.swift Tests/LinuxMain.swift
$ make sourcery 
sourcery --sources Source/SwiftLintFramework/Rules --templates .sourcery/PrimaryRuleList.stencil --output .sourcery
No config file provided or it does not exist. Using command line arguments.
Scanning sources...
error: The loaded '_InternalSwiftSyntaxParser' library is from a toolchain that is not compatible with this version of SwiftSyntax
The loaded '_InternalSwiftSyntaxParser' library is from a toolchain that is not compatible with this version of SwiftSyntaxmake: *** [Source/SwiftLintFramework/Models/PrimaryRuleList.swift] Error 3
$ xcode-select -p
/Applications/Xcode-12.4.app/Contents/Developer
$ xcodebuild -version
Xcode 12.4
Build version 12D4e

Given the following class structure:

protocol BaseProtocol {
	var variable: Int { get }
	func doSomething()
}

class BaseClass: BaseProtocol {
	var variable: Int = 0
	func doSomething() {}
}

protocol ExtendedProtocol: BaseClass {
	var externdedVariable: Int { get }
	func extendedDoSomething()
}

class ExtendedClass: BaseClass, ExtendedProtocol {
	var externdedVariable: Int = 0
	func extendedDoSomething() { }
}

When navigating the allMethods property of ExtendedProtocol, doSomething will appear twice, once with definedInTypeName = BaseClass and once with definedInTypeName = BaseProtocol. Interestingly, allVariables only contains variable once.

Example stencil file:

{% for protocol in types.protocols where protocol.name|hasSuffix:"ExtendedProtocol"  %}
class Mock{{ protocol.name|replace:"Protocol","" }}: {{protocol.name}} {

{% for variable in protocol.allVariables|!definedInExtension %}
    {{ variable.name }} coming from {{variable.definedInTypeName}}
{% endfor %}

{% for method in protocol.allMethods|!definedInExtension %}
    {{ method.name }} coming from {{method.definedInTypeName}}
{% endfor %}

}

{% endfor %}

This is particularly a problem when trying to generate mocks. Using the current AutoMockable.stencil, the generated mock will not compile, because all the helpers generated for doSomething will be created twice.

I'm seeing an error whenever I try to generate files using Sourcery. The error looks like this:

error: Error Domain=NSCocoaErrorDomain Code=4 "“SwiftTemplate” couldn’t be moved to “Mock.swifttemplate” because either the former doesn’t exist, or the folder containing the latter doesn’t exist." UserInfo={NSSourceFilePathErrorKey=/var/folders/4s/kz_7_74j6y9dgr4zv1zty5w40000gn/T/SwiftTemplate/0.16.0/.build/debug/SwiftTemplate, NSUserStringVariant=(
    Move
), NSDestinationFilePath=/Users/max/Library/Caches/Sourcery/Mock.swifttemplate/68oTZ5uoc%2FNLqYRTuvHnzYxhRGfxDXdvwT7dDod7lWc%3D, NSFilePath=/var/folders/4s/kz_7_74j6y9dgr4zv1zty5w40000gn/T/SwiftTemplate/0.16.0/.build/debug/SwiftTemplate, NSUnderlyingError=0x7f80c04e5800 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

I'm seeing this error on Sourcery 0.16.0 as well as on the latest master branch. (I built the latter with Xcode 10.2). Running Mojave 10.14.4.

I see two other issues that look like they're related, but both were closed without an apparent resolution. The suggestion to clean the ~/Library/Caches/Sourcery folder did not work for me.

Related issues: https://github.com/krzysztofzablocki/Sourcery/issues/739 https://github.com/krzysztofzablocki/Sourcery/issues/741

It also appears this PR (https://github.com/krzysztofzablocki/Sourcery/pull/744) was meant to fix the issue, but again I'm still seeing it on the latest master.

I'm getting an error running Sourcery since I passed to Xcode 10 and updated Sourcery to 0.14.0:

No config file provided or it does not exist. Using command line arguments.
Scanning sources...
Found 676 types.
Loading templates...
Loaded 5 templates.
Generating code...
error: Error Domain=NSOSStatusErrorDomain Code=-1 "kCFStreamErrorHTTPParseFailure / kCFSocketError / kCFStreamErrorDomainCustom / kCSIdentityUnknownAuthorityErr / qErr / telGenericError / dsNoExtsMacsBug / kMovieLoadStateError / cdevGenErr: Could not parse the request/response. /  / custom to the kind of stream in question  /  / queue element not found during deletion /  / not a SysErr, just a placeholder  /  / General error; gray cdev w/o alert" UserInfo={terminationReason=__ObjC.Process.TerminationReason, error=dyld: Symbol not found: __T0BOWV
  Referenced from: /Users/david/Library/Caches/Sourcery/AutoCodable.swifttemplate/../SourceryRuntime.framework/Versions/A/SourceryRuntime
  Expected in: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx/libswiftCore.dylib
 in /Users/david/Library/Caches/Sourcery/AutoCodable.swifttemplate/../SourceryRuntime.framework/Versions/A/SourceryRuntime
}

Im trying to loop over repeated annotations, except sometimes they might not be repeated.

How can I treat the annotation as an array even if it's only a single value?

As stated in issue #551, current type declaration only provides a boolean flag stating whether a type has a generic declaration or not. This PR parses the list of generic types associated to a type declaration as an Array<String>. They can be accessed during generation through the property type.genericTypes. Default value (when type is not generic) is an empty array.

This pull request is to address issue #1072: adding support for mocking class methods

As no object is created when calling a class method, keeping track of calls is done on static variable and a reset method is added to reset the mock between tests

Since Swift 5.7, Swift provides language-level support for distributed actors. Distributed actors can be defined using the distributed actor keywords. On distributed actors, one can define distributed methods using distributed func. For example:

distributed actor HelloActor {
    init(actorSystem: ActorSystem) {
        self.actorSystem = actorSystem
    }

    distributed func hello() {
        print("Hello!")
    }
}

Sourcery currently does not seem to provide a way to inspect if an actor or method is declared as distributed, for example with an isDistributed property on Actor or Method.

With code like this

@available(iOS, introduced: 2.0, deprecated: 12.0, message: "No longer supported; please adopt WKWebView.")
@_Concurrency.MainActor open class UIWebView : UIView, NSCoding, UIScrollViewDelegate {
}

The type attributes.available will return this

[@available(iOS, introduced: 2.0, deprecated: 12.0, message: \)]

Env

Sourcery: 1.9.2 Xcode: Version 14.2 macOS: 13.1 (22C65)

I am new to Sources and setting up using SPM command plugin.

• In the Package.swift file .package(url: "https://github.com/krzysztofzablocki/Sourcery.git", revision: "3a9e5f1014ac09b30727c01d2a0e1531dac30948") (use commit of 1.9.2 release, due to https://github.com/krzysztofzablocki/Sourcery/issues/1102 issue.)

• $ swift package plugin --list output ‘sourcery-command’ (plugin ‘SourceryCommandPlugin’ in package ‘Sourcery’)

• Running swift package --allow-writing-to-package-directory sourcery-command failed with error error: the library 'ArticleCardFeature' requires macos 10.13, but depends on the product 'ComposableArchitecture' which requires macos 10.15; consider changing the library 'ArticleCardFeature' to require macos 10.15 or later, or the product 'ComposableArchitecture' to require macos 10.13 or earlier. and the same error for every feature module.

Do I miss something in configuration?

SelectCategoriesModel.swift

enum SelectCategories {
  struct SelectCategoryViewModel {
    let id: String
    let text: String
    let imageName: String?
    let isSelected: Bool
  }
}

extension SelectCategories.SelectCategoryViewModel: AutoLenses { }

Lens+Generated.swift

extension SelectCategories.SelectCategoryViewModel {
  static let idLens = Lens<SelectCategories.SelectCategoryViewModel, String>(
    get: { $0.id },
    set: { id, selectcategories.selectcategoryviewmodel in
    
       SelectCategories.SelectCategoryViewModel(id: id, text: selectcategories.selectcategoryviewmodel.text, imageName: selectcategories.selectcategoryviewmodel.imageName, isSelected: selectcategories.selectcategoryviewmodel.isSelected)
    }
  )
  static let textLens = Lens<SelectCategories.SelectCategoryViewModel, String>(
    get: { $0.text },
    set: { text, selectcategories.selectcategoryviewmodel in
       SelectCategories.SelectCategoryViewModel(id: selectcategories.selectcategoryviewmodel.id, text: text, imageName: selectcategories.selectcategoryviewmodel.imageName, isSelected: selectcategories.selectcategoryviewmodel.isSelected)
    }
  )
  static let imageNameLens = Lens<SelectCategories.SelectCategoryViewModel, String?>(
    get: { $0.imageName },
    set: { imageName, selectcategories.selectcategoryviewmodel in
       SelectCategories.SelectCategoryViewModel(id: selectcategories.selectcategoryviewmodel.id, text: selectcategories.selectcategoryviewmodel.text, imageName: imageName, isSelected: selectcategories.selectcategoryviewmodel.isSelected)
    }
  )
  static let isSelectedLens = Lens<SelectCategories.SelectCategoryViewModel, Bool>(
    get: { $0.isSelected },
    set: { isSelected, selectcategories.selectcategoryviewmodel in
       SelectCategories.SelectCategoryViewModel(id: selectcategories.selectcategoryviewmodel.id, text: selectcategories.selectcategoryviewmodel.text, imageName: selectcategories.selectcategoryviewmodel.imageName, isSelected: isSelected)
    }
  )
}

It fails to compile because the setter parameter name matches the type name, which contains a dot character.

I have a secret that ends in "==" and am having trouble using sourcery to convert that secret into my stencil.

Steps to reproduce:

1. Install Sourcery with brew brew install sourcery
2. Create a simple stencil, Secrets.stencil like the following

public struct Secrets {
    public var vendor: VendorSecrets
    
    public struct VendorSecrets {
        public var credentials: String
    }
}

public var secrets = Secrets(
    vendor: .init(
        credentials: "{{ argument.VENDOR_CREDENTIALS }}"
    )
)

3. Run the following command in a terminal

export VENDOR_CREDENTIALS="banana==" && sourcery \
    --templates . \
    --sources . \
    --output . \
    --args VENDOR_CREDENTIALS=$VENDOR_CREDENTIALS

Result: Sourcery will produce Secrets.generated.stencil that looks like the following

// Generated using Sourcery 1.9.0 — https://github.com/krzysztofzablocki/Sourcery
// DO NOT EDIT
public struct Secrets {
    public var vendor: VendorSecrets

    public struct VendorSecrets {
        public var credentials: String
    }
}

public var secrets = Secrets(
    vendor: .init(
        credentials: "1" // Uh oh
    )
)

Expected result: Sourcery will produce Secrets.generated.stencil that looks like the following

// Generated using Sourcery 1.9.0 — https://github.com/krzysztofzablocki/Sourcery
// DO NOT EDIT
public struct Secrets {
    public var vendor: VendorSecrets

    public struct VendorSecrets {
        public var credentials: String
    }
}

public var secrets = Secrets(
    vendor: .init(
        credentials: "banana=="
    )
)

OS: macOS 12.6.1 (M1 Max)