Skip to content

Documentation on how to use it is not clear enough #7

@rogerluan

Description

@rogerluan

Hi there! 👋

I'd love to give this tool a try, but I found myself stuck in the how-to-use step. It might be my ignorance, but I don't understand how the --files-to-modules works. From the documentation:

File paths each containing a map of source files and corresponding module names.

How should this map be constructed? Can you give real examples?

There're many different project setups possible and the README doesn't mention any "supported setups" nor "unsupported setups". For instance, the project might be a .xcodeproj, or .xcworkspace, it may have pod dependencies, or SPM dependencies. The project might be a SPM on its own, with or without dependencies, etc. At this point I'm not sure if this tool is universal and would work with any project.

Looking forward for more info! 🤗 thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions