jpsim / jpsim/SourceKitten

Swift framework with displayed classes and methods declaration

Open
#576 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
2.4k
Forks
237
PR merge metrics
No merged PRs in 30d

Description

Hi @jpsim

I was discussing with you on the #405 issue, I'm actually creating my swift framework and I want to make my classes and methods declarations visible to my framework users.

After creating my cocoa touch framework and generating it, only a projectName-swift.h class appear under headers folder, and this class does not contain my classes or methods declarations already created with public key.

And like I want to make these declarations visible to my framework users I thought about generating a swift interface containing all the declarations I made. the same like the interface generated by Xcode on related items.
I used your req.yml file to generate the interface but only the content of my project name-swift.h was generated(does not contain any important thing for me).

What I want to know, is this the best way to make my classes and methods visible for my swift framework users ?
if it's not do you have any suggestion for me ? should I make the framework on obj-c to make declarations visible in header file like before...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the discussion in issue #405 and the req.yml configuration used to generate the interface. Compare the generated projectName-swift.h output with the declarations shown by Xcode, then clarify whether the requested framework-visible declarations are a SourceKitten feature; done means a documented, reproducible approach or a defined implementation scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.