Automatically resolve types across modules

[krishnaagarwal1994]

I am parsing a method in a class A present in TargetA,
Class A has a method that has a return type of Class B, which is also present in TargetA.
But sourcery is still returning false for

{{ method.returnType }} -> nil
{{ method.returnTypeName }} -> ClassB

The configuration file that I am using

project:
  - file: #path to project file
    target:
      name: TargetA
templates:
    - SourceryTemplates
output: src/Generated

[krishnaagarwal1994]

@ilyapuchka Can you please help me with this?
Thank You.

[krzysztofzablocki]

@krishnaagarwal1994 can you create a sample project reproducing the issue? it would help

[krishnaagarwal1994]

sourcery0.zip
Hi @krzysztofzablocki , thanks for your response.
I have created a sample project, in which I am able to reproduce the problem.
Please have a look into it, and do let me know in case you have any questions regarding this Sample Project.
Thanks.

[krzysztofzablocki]

thanks, I don't think we ever had cross module resolution with not fully qualified names, if you add the target name explicitly to getStudentB() -> CustomTarget.Student then it gets all information,

I'll look into adding this feature

[krishnaagarwal1994]

@krzysztofzablocki Yeah, I already tried that, if mentioning the target name explicitly then it's identifying correctly.
Also, I would like to share one more finding with you.

If I am mentioning project path, target names then the Sourcery is retuning the returnType as nil
But if you simply provide the target files path using the source attribute in the Sourcery configuration file then it's able to identify the returnType.

[krishnaagarwal1994]

@krzysztofzablocki
Changing the sourcery.yml file contents to below is giving the right results.

sources:
  - CustomTarget
  - CustomTargetB
templates:
    - SourceryTemplates
output: Generated

[krzysztofzablocki]

yeah sources don't run into those kind of issues, that's original implementation and more popular, xcodeproj was contributed later and there are some kinks there to figure out

I'm going to try to implement this either way, but not sure when so if you don't need xcodeproj integration it's easier to use sources approach

[krishnaagarwal1994]

Actually, I am working on a quite complex project, where I need to support functionality on a module/target level.
At some places the physical path and logical path of files are different. and some files belong to more than one target.
So rather than relying on physical paths for the modules, I would love to use the project-target functionlity of the Sourcery configuration file.
Also thanks for all the help and support.

[krishnaagarwal1994]

@krzysztofzablocki Thanks for the fix.