Skip to content

Improve handling of optional requirements in gemspec #3

@trans

Description

@trans

When generating a gem, make sure a dependency in the optional group is not added to the gemspec.

Not sure how to handle the case when a requirement is both an optional runtime dependency and a development dependency.

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